Re: [CORE] postpone next week's release

From: David Steele <david(at)pgmasters(dot)net>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, 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-31 01:51:04
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 5/30/15 8:38 PM, Joshua D. Drake wrote:
> On 05/30/2015 03:48 PM, David Steele wrote:
>> On 5/30/15 2:10 PM, Robert Haas wrote:
>>> What, in this release, could break things badly? RLS? Grouping sets?
>>> Heikki's WAL format changes? That last one sounds really scary to me;
>>> it's painful if not impossible to fix the WAL format in a minor
>>> release.
>> I would argue Heikki's WAL stuff is a perfect case for releasing a
>> public alpha/beta soon. I'd love to test PgBackRest with an "official"
>> 9.5dev build. The PgBackRest test suite has lots of tests that run on
>> versions 8.3+ and might well shake out any bugs that are lying around.
> You are right. Clone git, run it nightly automated and please, please
> report anything you find. There is no reason for a tagged release for
> that. Consider it a custom, purpose built, build-test farm.

Sure - I can write code to do that. But then why release a beta at all?

- David Steele

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Karlsson 2015-05-31 02:14:34 [PATCH] Reload SSL certificates on SIGHUP
Previous Message Kouhei Kaigai 2015-05-31 01:03:31 [idea] more aggressive join pushdown on postgres_fdw