Re: [nant-dev] NAnt Tag and Branch policies

[Ian MacLean]

From my reading of the docs they are not orthogonal. ie when you are 
satisfied that the source is in a releasable state then you add the 
rtags so you can always get that version at a later date. Branching 
however gives you a seperate dev line which enables you to polish a 
release while still making changes to the main branch. If you choose not 
to branch and the release process takes any length of time then all the 
commits waiting to go onto the main line have to be queued up. If a 
branch is made the sources should still be rtagged on that branch prior 
to release - its not really an either/or situation.

see: http://www.kagekaze.org/cvs/cvs-talk/releng/tags.html

Ian

I'm not a cvs expert, but it seems like we are not doing this correctly if
we create a branch before we make a release. We should be rtag'n and not
branch'n.
----- Original Message ----- 
From: "Clayton Harbour" <[EMAIL PROTECTED]>
To: "Scott Hernandez" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Wednesday, November 12, 2003 7:43 PM
Subject: RE: [nant-dev] NAnt Tag and Branch policies

 





-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers