public inbox for [email protected]  

help / color / mirror / Atom feed

From: Kevin Brown <[email protected]>
To: Matthew T. O'Connor <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: Christopher Kings-Lynne <[email protected]>
Cc: PostgreSQL Development <[email protected]>
Subject: Re: Release cycle length
Date: Mon, 17 Nov 2003 19:26:20 -0800
Message-ID: <20031118032620.GK6073@filer> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

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					      [email protected]

view thread (83+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Release cycle length
  In-Reply-To: <20031118032620.GK6073@filer>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox