ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan.Mate...@rzf.fin-nrw.de
Subject AW: Ant 1.6.3 [was status report on the PMC list]
Date Wed, 25 Aug 2004 13:48:19 GMT
Forrest switched to SVN, for example.

Jan

> -----Urspr√ľngliche Nachricht-----
> Von: Dominique Devienne [mailto:DDevienne@lgc.com]
> Gesendet am: Mittwoch, 25. August 2004 15:46
> An: Ant Developers List
> Betreff: RE: Ant 1.6.3 [was status report on the PMC list]
> 
> > From: Conor MacNeill [mailto:conor@cortexebusiness.com.au]
> > The choices I see for branch management are:
> > 
> > 1. Keep going the way we are now - i.e. applying changes to 
> both HEAD
> > and the active branch.
> > 
> > 2. Keep going as we do now but make sure branches are shorter lived.
> The
> >    impact of this would be to have fewer micro releases and 
> more minor
> > releases. i.e. instead of Ant 1.6.3, we would go from HEAD 
> and call it
> > Ant 1.7 even though it may not contain any significant new features.
> 
> Semi-automated repeated CVS merges between branches are very prone
> to issues. Manual merges are prone to the human error factor too ;-)
> 
> Another more controversial alternative would be to use a CM tool
> with better merging abilities, and Subversion comes to mind of course.
> From the little I've read, it seems that SVN does merges 
> better, without
> the need for tags, thanks to its global versioning of the whole repo.
> 
> Is there an official line of the ASF about SVN? And are there any
> Apache projects which have switched to SVN? Just wondering, --DD
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
> 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message