Re: [CORE] postpone next week's release - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [CORE] postpone next week's release
Date
Msg-id CA+Tgmoadg9dHLpWodfwDaTZ=RbW+C_4CrgYyZ=Vx5QpMyP=N5A@mail.gmail.com
Whole thread Raw
In response to Re: [CORE] postpone next week's release  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [CORE] postpone next week's release  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, May 29, 2015 at 4:01 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> It's possible that we ought to give up on a pre-conference beta.
> Certainly a whole lot of time that I'd hoped would go into reviewing
> 9.5 feature commits has instead gone into back-branch bug chasing this
> week.

I'm personally kind of astonished that we're even thinking about beta
so soon.  I mean, we at least need to go through the stuff listed
here, I think:

https://wiki.postgresql.org/wiki/PostgreSQL_9.5_Open_Items

The bigger issue is: what's NOT on that list that should be?  I think
we need to devote some cycles to figuring that out, and I sure haven't
had any this week.

In any case, I think the negative PR that we're going to get from not
getting this multixact stuff taken care of is going to far outweigh
any positive PR from getting 9.5beta1 out a little sooner, especially
if 9.5beta1 is bug-ridden because we gave it no time to settle.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Need Force flag for pg_drop_replication_slot()
Next
From: Stephen Frost
Date:
Subject: Re: Need Force flag for pg_drop_replication_slot()