Re: [CORE] RC1 blocker issues

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [CORE] RC1 blocker issues
Date: 2006-11-27 01:04:02
Message-ID: 659.1164589442@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Josh Berkus wrote:
>> Overall, I submit that our release process is broken, and that we're
>> having trouble getting this release out because nobody is paying
>> attention to it (of which I too have been guilty off-and-on).

> We also have this issue every year, but the time from beta to release
> has always been about three months. With the buildfarm helping out,
> we're a couple of weeks early this time. Rejoice.

I'm not sure that the process is broken, but I agree that there's been
way too little focus on testing this time around; it seems that most of
the chatter on pgsql-hackers since beta started has been about ideas for
8.3 development. Have we caused that by deciding to have a short 8.3
devel cycle, ie, do people feel they needed a head start? If so, it's
bad, but the damage is already done, and won't be repeated as long as we
go back to a more normal schedule after 8.3. If there's another force
at work, what is it?

I am a bit worried about this, because we're predicating the decision
to release 8.2 now on the lack of bug reports; if that's due to lack of
testing rather than lack of bugs, we might have a disaster in the
making. But there's no way to know that now, and really I see no value
in being fearful at this point. If we delayed a month, we'd be in
pretty much just the same situation a month from now.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Theo Schlossnagle 2006-11-27 01:11:13 Re: [CORE] RC1 blocker issues
Previous Message Mark Kirkwood 2006-11-27 00:52:46 Re: [PATCHES] Avg performance for int8/numeric