Re: Last gasp

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Last gasp
Date: 2012-04-08 22:16:50
Message-ID: 4F820E52.3040006@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> In short, the idea of strongly calendar-driven releases looks more
> and more attractive to me the more times we go through this process.
> If your patch isn't ready on date X, then it's not getting into this
> release; but there'll be another bus coming along before long.
> Stretching out release cycles to get in those last few neat features
> just increases the pressure for more of the same, because people don't
> know how long it will be to the next release.

As you know, I've supported this view for several years.

> Just to be clear ... I don't believe that we can have hard-and-fast
> *release* dates. I am suggesting that it might be a good idea to have
> a hard deadline for committing new features. But beta test phase will
> take however long it takes. I don't think shaking out bugs is a
> predictable process.

It could have more visibility though, which would probably also make it
go faster. Something to work on.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2012-04-08 23:00:34 Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)
Previous Message Peter Eisentraut 2012-04-08 21:04:29 Re: Is there any way to disable compiler optimization and enable debug?