You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Peter C <pe...@gmail.com> on 2008/04/26 01:32:28 UTC
Best way to create new version
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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Best way to create new version
Posted by Peter C <pe...@gmail.com>.
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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Best way to create new version
Posted by Blair Zajac <bl...@orcaware.com>.
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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Best way to create new version
Posted by "Harvey, Edward" <Ed...@patni.com>.
> 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.
Fortunately, this is relatively easy.
svn cp svn://server/repository/trunk svn://server/repository/branches/ver2
Then, whoever is working on bug fixes for ver2 can work in the new "ver2" branch.
Whoever is working on new features, for ver3, ver4, etc continue to work in trunk.
This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at netadmin@patni.com and delete this mail.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Best way to create new version
Posted by Matt imMute Sickler <im...@msk4.ath.cx>.
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@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org