Re: Release cycle length
Kevin Brown <kevin@sysexperts.com>
From: Kevin Brown <kevin@sysexperts.com>
To: "Matthew T. O'Connor" <matthew@zeut.net>
Cc: Peter Eisentraut <peter_e@gmx.net>, "Marc G. Fournier" <scrappy@postgresql.org>, Christopher Kings-Lynne <chriskl@familyhealth.com.au>, PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: 2003-11-18T03:26:20Z
Lists: pgsql-hackers
Matthew T. O'Connor wrote: > I agree with Peter's other comment, that the longer the development > cycle, the longer the beta / bug shakeout period, perhaps a shorter dev > cycle would yield a shorter beta period, but perhaps it would also > result in a less solid release. Perhaps. Perhaps not. The fewer the changes, the less complexity you have to manage. But it would certainly result in a smaller set of feature changes per release. Some people might regard that as a good thing. The advantage to doing more frequent releases is that new features end up with more real-world testing within a given block of time, on average, because a lot more people pick up the releases than the CVS snapshots or even release candidates.. -- Kevin Brown kevin@sysexperts.com