Good advice :) I was trying to get this release "perfect" since it's our graduation release, but you're right - we will always be issuing frequent fixes and improvements.
-T On Sun, Jan 3, 2010 at 12:02 AM, Niclas Hedhman <[email protected]> wrote: > On Sun, Jan 3, 2010 at 7:04 AM, Todd Volkert <[email protected]> wrote: > > then maybe they should block a release. > > General piece of advice; Try to make your release procedure very > efficient, press of a button if possible, so that you can fill the > "Release Early, Release Often" mantra. > The idea is that; No matter how much you test and spend time to get > things right, you will miss something. By getting a release out to > initially dozens, later on thousands, of people will give you a LOT of > feedback of things that doesn't work. The importance is short feedback > cycle. > Release -> Feedback -> Fix -> Release, should preferably be "some few" > weeks in lenghts. Exactly what "few" stands for is a product of > community activity, effort required to cut the release, the PMC's > ability to vet the release and ASF infratstructure's ability to spread > it. > The last one can be ignored, since it is nowadays a matter of hours. > PMC's vetting will in reality be proportional to the cycle. Small > increments in the release, means less things to check. > Community Activity is whether there is a body of people who are eager > to use the newly released stuff. > > So, if the effort required by the Release Manager is near zero, there > is no reason not to make a release even with minimal changes in it, > and with that attitude there is no reason to hold up a release because > "we know of a bug". Just churn out those releases, I would recommend > 2-6 weeks if possible... :-) > > > Cheers > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java > > I live here; http://tinyurl.com/2qq9er > I work here; http://tinyurl.com/2ymelc > I relax here; http://tinyurl.com/2cgsug >
