Re: Plan for feature freeze? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Plan for feature freeze?
Date
Msg-id 200405010122.i411Msi27828@candle.pha.pa.us
Whole thread Raw
In response to Re: Plan for feature freeze?  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Responses Re: Plan for feature freeze?  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-hackers
Maybe we should take a vote on the cuttoff date scheduling.  Marc, is
this something that can be voted on by the group?

---------------------------------------------------------------------------

Tatsuo Ishii wrote:
> > > >>Why don't we just set a freeze of August 1st? Give everyone just a
> > > >>little extra time. No float. If it doesn't make
> > > >>it by August 1st, it doesn't make it.
> > > >>
> > > >>
> > > >
> > > >We could go for September 1st, which would mean most are back from
> > > >holidays, in order to do beta testing ... and no, I'm not serious ...
> > > >
> > > >
> > > >
> > > Why not? Seemed like a fairly good argument both yours and mine ;)
> > 
> > To me, it ranks up there with "lets freeze someday in the future" ...
> 
> For me even September 1st does not seem too late. Major version up
> bring users pains including backup/restore application
> imcompatibilty... IMO to justify those pains we need to give users
> major enhancements. Honestly I don't understand why we should rush the
> major version up.
> --
> Tatsuo Ishii
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
> 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: pg ANY/SOME ambiguity wrt sql standard?
Next
From: Tom Lane
Date:
Subject: Re: Weird prepared stmt behavior