Forgot the link: http://www.enteract.com/~bradapp/acme/branching/branch-creation.html#Codelin ePerMajorRelease
> -----Original Message----- > From: Jordan, Tom [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, August 14, 2002 10:34 AM > To: '[EMAIL PROTECTED]' > Subject: RE: [nant-dev] NAnt 0.9 refactoring (long) > > > > From: Ian MacLean [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, August 13, 2002 4:13 PM > > > > I tend to agree. Is this what other open source projects are > > doing ? And etc > > Basically, yes. > The mainline is always for forward development, while branches > are reserved for fixes to release drops. > > As far as maintaining multiple releases of a product, in my > devRoot workspace, I create a <productRoot> directory. > Then I check out the release branches into sub directories. > eg: (one scenario) > /devRoot > /nant-dev > /1.0 > /nant <- branch: nant--1_0--main--br > /1.5 > /nant <- branch: nant--1_5--1_0--br > /2.0 > /nant <- branch: nant--2_0--main--br > /mainline > /nant <- branch: HEAD > > See: > > > ------------------------------------------------------- > This sf.net email is sponsored by: Dice - The leading online job board > for high-tech professionals. Search and apply for tech jobs today! > http://seeker.dice.com/seeker.epl?rel_code=31 > _______________________________________________ > Nant-developers mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers > ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
