Ideally, the trunk should be thought of as being "version x.y" rather it
should be thought of as "bleeding edge". Versioned releases should go
in tags, and updates to those releases should go in branches. Thus tags
are static and branches (at least the legacy branches) would get
bugfixes and updates.
Peter C wrote:
> Hello,
> I am pretty new with svn, so bare with me. I have a svn
> repository which is divided into trunk (source files), tags and
> branches. The current source is at version 2.x, which have been release
> to end users for sometime. Now there is need to add more features and
> new version 3.0 to be developed. Here is the situation, I would like
> keep working on new version 3 at the same time still maintaining version
> 2.x. Since both versions shares lots of code, only differ of in terms of
> new features.
>
> I am thinking of creating a new branch for version 3 and leave
> trunk as version 2. Is this the best way to go about it ?
>
>
> Peter.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-28 18:12:05 CEST