Re: Plan for feature freeze?

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: scrappy(at)postgresql(dot)org
Cc: jd(at)commandprompt(dot)com, pgman(at)candle(dot)pha(dot)pa(dot)us, tgl(at)sss(dot)pgh(dot)pa(dot)us, andrew(at)dunslane(dot)net, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Plan for feature freeze?
Date: 2004-05-01 00:53:50
Message-ID: 20040501.095350.10290718.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > >>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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-05-01 00:56:54 Re: pg ANY/SOME ambiguity wrt sql standard?
Previous Message Bruce Momjian 2004-05-01 00:24:32 Re: ecpg and the timezone database