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

From David Steele
Subject Re: [CORE] postpone next week's release
Date
Msg-id 556A6908.8080600@pgmasters.net
Whole thread Raw
In response to Re: [CORE] postpone next week's release  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: [CORE] postpone next week's release  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: [CORE] postpone next week's release  (Noah Misch <noah@leadboat.com>)
Re: [CORE] postpone next week's release  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
List 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
david@pgmasters.net


pgsql-hackers by date:

Previous
From: Kouhei Kaigai
Date:
Subject: [idea] more aggressive join pushdown on postgres_fdw
Next
From: Andreas Karlsson
Date:
Subject: [PATCH] Reload SSL certificates on SIGHUP