I think version 2 will be more of a bug fixes. Leaving latest version
in trunk, seems to make sense. I will check the svn documents, I am
still not familiar with branches and etc.
Thanks.
On 26 Apr 2008, at 9:42 AM, Blair Zajac wrote:
> 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 ?
>
> Sure, you could do that route or branch trunk for version 2 and do
> development on version 3 in trunk. It's a style issue, but trunk
> would see more of your active development. If version 2 is only
> getting minor changes, then I would make version 2 a branch.
>
> Also, think when you have version 4. Most likely you wouldn't want
> to branch 4 from 3's branch, so basically, keep the newest version
> on trunk.
>
> Blair
---------------------------------------------------------------------
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-26 04:28:08 CEST