Re: Two weeks to feature freeze - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: Two weeks to feature freeze
Date
Msg-id 20030619222026.C51411@hub.org
Whole thread Raw
In response to Re: Two weeks to feature freeze  ("Andrew Dunstan" <andrew@dunslane.net>)
Responses Re: Two weeks to feature freeze
Re: Two weeks to feature freeze
List pgsql-hackers
On Thu, 19 Jun 2003, Andrew Dunstan wrote:

>
> Maybe a better strategy would be to get a release out soon but not wait
> 6 months for another release which would contain the Win32 port and the
> PITR stuff (assuming those aren't done in time for this release).
>
> Just a thought.

And definitely in agreement here ... I'd rather see a shortened dev cycle
prompted by a big feature being added, then delaying a release because "oh
oh, I need another few weeks" that draws out when something unexpected
happens :(
> > andrew
>
> Tom Lane wrote:
> > Robert Treat <xzilla@users.sourceforge.net> writes:
> >> Well, I suppose that history has shown that waiting on specific
> >> features causes trouble with postgresql development, but I don't see
> >> why a release can't be based around waiting for feature x as long as
> >> feature x is being actively worked on by trusted developers who have
> >> an endgame in sight.
> >
> > We have been led down that garden path before, and it's been a losing
> > proposition every time.
> >
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org


pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: allowed user/db variables
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Re: add column .. default