Re: DarwinPorts 1.3.1

On Aug 1, 2006, at 7:48 PM, Landon Fuller wrote:

> If the release process isn't ferreting out bugs, or is not agile  
> enough to incorporate fixes quickly enough, do you have a  
> suggestion for improving the situation?

what's preventing the release process from incorporating the fixes?

It sounds like DarwinPorts is evolving toward the FreeBSD STABLE/ 
CURRENT model[1], where STABLE code is vetted and solid, even if it  
changes regularly -- you can follow the branch safely and pickup  
fixes as they come along -- while CURRENT changes much more rapidly  
and isn't guaranteed to work, though testing is encouraged.

> Telling users to switch to CVS for the latest changes negates the  
> purpose of doing releases at all, which was to shield users from  
> unstable code in HEAD.

Perhaps the CVS tree needs to reflect the reality of a STABLE branch  
that doesn't include enough changes to warrant a release tag but  
still contains incremental improvements that users needs.

[1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current- 
stable.html#STABLE
--
Paul Beard
contact info: www.paulbeard.org/paulbeard.vcf

Are you trying to win an argument or solve a problem?