Re: [CORE] postpone next week's release

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, pgsql-core <pgsql-core(at)postgresql(dot)org>
Subject: Re: [CORE] postpone next week's release
Date: 2015-05-30 14:06:52
Message-ID: CA+TgmoYovkev0xXnxaTD8vnt=M9Cn+RmOkVEouqwj6_9JLkzLw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, May 30, 2015 at 12:08 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I think your position is completely nuts. The GROUPING SETS code is
> desperately in need of testing. The custom-plan code is desperately
> in need of fixing and testing. The multixact code is desperately
> in need of testing. The open-items list has several other problems
> besides those. All of those problems are independent. If we insist
> on tackling them serially rather than in parallel, 9.5 might not come
> out till 2017.

If that means it's stable, +1 from me.

I dispute, on every level, the notion that not releasing a beta means
that we can't work on things in parallel. We can work on all of the
things on the open items list in parallel right now. We can also
test. And in fact, we should test. It's entirely appropriate to test
our own stuff before we ask other people to test it. It's also
appropriate to fix the things that we already know are broken before
we ask other people to test it.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2015-05-30 14:11:09 Re: [CORE] postpone next week's release
Previous Message Bruce Momjian 2015-05-30 13:11:40 Re: [CORE] postpone next week's release