| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-29 22:33:21 |
| Message-ID: | 20150529223321.GB6535@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-05-29 18:02:36 -0400, Robert Haas wrote:
> Well, I think we ought to take at least a few weeks to try to do a bit
> of code review and clean up what we can from the open items list.
Why? A large portion of the input required to go from beta towards a
release is from actual users. To see when things break, what confuses
them and such.
I don't see why that requires that there are no minor entries in the
open items list - and that's what currently is on it. Neither does it
seem to be a problem to do code review concurrently to user beta
testing. We obviously can't start a beta if things crash left and
right, but I don't think that's the situation right now?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2015-05-29 22:41:01 | Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |
| Previous Message | Robert Haas | 2015-05-29 22:29:46 | Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |