Re: commit fest status and release timeline

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Vik Fearing <vik(dot)fearing(at)dalibo(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: commit fest status and release timeline
Date: 2014-03-02 03:56:42
Message-ID: CAB7nPqTeHkSLGHxc0G2jzyhnc2RVaV0eCtMqAT4VraZphJNLDQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Mar 2, 2014 at 7:43 AM, Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> wrote:
> On 03/01/2014 07:50 PM, Josh Berkus wrote:
>> On 03/01/2014 09:01 AM, Peter Eisentraut wrote:
>>> Status Summary. Needs Review: 36, Waiting on Author: 7, Ready for
>>> Committer: 16, Committed: 43, Returned with Feedback: 8, Rejected: 4.
>>> Total: 114.
>>>
>>> We're still on track to achieve about 50% committed patches, which would
>>> be similar to the previous few commit fests. So decent job so far.
>> So, other than Hstore2/JSONB and Logical Changesets, what are the
>> big/difficult patches left?
>
> For me, I'd really like to see the reduced locks on ALTER TABLE.
The patch by Peter to improve test coverage for client programs. This
is helpful for QE/QA teams evaluating Postgres, and it could be
extended for other things like replication test suite as well as far
as I understood.
Regards,
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabrízio de Royes Mello 2014-03-02 04:04:47 Re: Patch to add support of "IF NOT EXISTS" to others "CREATE" statements
Previous Message Tom Lane 2014-03-02 02:43:19 Re: Securing "make check" (CVE-2014-0067)