Rich Freeman posted on Wed, 21 Sep 2011 10:46:38 -0400 as excerpted: > An issue your suggestion doesn't address is when packages don't even > stick around 30 days/etc. > > I know I've seen many packages where there is an ancient stable version > that is never touched, and a much newer ~arch version that gets tweaked > every 3-6 weeks. When it gets tweaked, often the old version is just > removed immediately, or shortly after it is bumped. So, packages often > don't stick around the 30 days it takes to stabilize them. > > Granted, this is a bit anecdotal so I can't speak for how big a problem > this is in reality. However, for any stabilization scheme to work > packages have to be, well, stable. :)
Talking about... Just today I was reading that the firefox folks are debating shortening the current 6-week cycle to 5-weeks or less. http://www.h-online.com/open/news/item/Mozilla-developers-consider-even-shorter-release-cycle-1347013.html -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
