Re: Per tuple overhead, cmin, cmax, OID - Mailing list pgsql-hackers

From Marc G. Fournier
Subject Re: Per tuple overhead, cmin, cmax, OID
Date
Msg-id 20020609020247.H27088-100000@mail1.hub.org
Whole thread Raw
In response to Re: Per tuple overhead, cmin, cmax, OID  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Sat, 8 Jun 2002, Bruce Momjian wrote:

> It is the idea were are supposed to go into beta with a bug-free release
> that bother me.

But its you that's always tried to advocate that ... no?  If not, then I
am confused, cause I know *I've* never ... to me, switching to beta mode
has always been the switch from 'add features' to 'fix the bugss to
release' ...

> Agreed.  Let's split sometime during beta as soon as we are ready to
> work on 7.4. Sooner and we just double-patch for no purpose, later and
> we stall development.

No, let's split *at* beta ... I imagine there are several ppl out there
that have alot of work they wish to do, and sitting around twiddling their
thumbs waiting for someone to *maybe* report a bug in their area/code is a
waste of everyone's time ... not to mention a delay in being ready to
release the next version ...

Hell, each 'beta period' we've done so far has caused that ... where we
get in patches and changes that aren't appropriate for beta and they get
sat on until after its been released ... then you risk the fun of merging
in conflicting changes, so the patch that was perfect when it was
submitted has to be redone because someone else's patch changed enough to
the code that it doesn't apply cleanly ...

Its not like it was years ago when there were a couple of us in the code
... there are enough developers out there now (and growing) that
'stalling' things isn't fair to them (or, in some cases, the companies
that are paying them to develop features) ...

We have the tools to do this, its time to start using them the way they
were meant to be used ...



pgsql-hackers by date:

Previous
From: Oliver Elphick
Date:
Subject: [Fwd: Re: [Fwd: Bug#149056: postgresql: should not try in a busy loop when allocating resources]]
Next
From: "Marc G. Fournier"
Date:
Subject: Re: Project scheduling issues (was Re: Per tuple overhead,