From: | Jason Earl <jason(dot)earl(at)simplot(dot)com> |
---|---|
To: | The Hermit Hacker <scrappy(at)postgresql(dot)org> |
Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Two weeks to feature freeze |
Date: | 2003-06-20 17:44:33 |
Message-ID: | 871xxoy77i.fsf@npa01zz001.simplot.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The Hermit Hacker <scrappy(at)postgresql(dot)org> writes:
> On Thu, 19 Jun 2003, Robert Treat wrote:
>
>> 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.
>
> Everyone has an 'endgame in sight', at least when they ask for a
> release to be postponed ... but then their date keeps slipping, etc
> ...
>
> The thing is, if win32 is 'that close to being finished', then as
> soon as v7.4 is out, that code should be ready to throw in ... and
> the same for every other features that could 'postpone a release'
> ...
>
> I'd rather see the dev cycle shortened by a month, then extended ...
Why couldn't you just release the win32 version of 7.4 when it was
finished. If it takes an extra month then that just gives you guys
the chance to circulate *two* press releases. The Native Win32 port
is likely to make a big enough splash all by itself.
Jason
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-06-20 18:00:14 | Commands to change name, schema, owner |
Previous Message | Nailah Ogeer | 2003-06-20 17:32:52 | Re: [HACKERS] psql |