Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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


pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group