12.09.06 20:51:31, Johnathan wrote:
Hi there

I'm new to the KDE Development Scene. And have some questions regarding
KDE SVN structure.

Reading through the subversion Tutorial at:

it states that the KDE repository is organized into:

* Trunk - The latest KDE development version. right now, KDE 4.
* Tags - Specific Release candidates e.g. KDE 3.5.2
* Branches - Version candidates (from browsing the websvn)? e.g. KDE 3.4,
KDE 3.5

Now, here are the 2 million 3 thousand 4 hundred 50 dollar and 50 cents
questions :D

Please have a look at

it explains you how trunk/branches/tags work together. Currently trunk
contains "bleeding edge", branches/KDE/3.5 contains the current stable
KDE version, tags//3.5.4 is just a "label" for /branches/KDE/3.5 at
the moment were KDE 3.5.4 was released.

1) What is the purpose for maintaining a Tags and Branches sections that
have what appear to me to be code overlaps?

No, SVN is smart enough to only store the differences between certain
revisions of a file.

Andreas

Tadeusz Andrzej Kadubowski wrote:
>2) As I understand it, Branches would just be the latest stable
>version of * Tags right?
>
way round. Tags are latest *stable* versions of branches.

Actually, neither.

The version branches are the stable branches of trunk. The tags are the
releases of the branches.

Aside from the version branches, there are also the work branches, which
are used to indicate some new feature or concept or rewrite being worked
on. They are mostly located in branches/work, but some are in the
application directories (for example, branches/kopete/0.12 contained
development code after it forked off branches/KDE/3.5).