Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2011-03-05T14:38:45Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Further refine patch for commenting operator implementation functions.

  2. Fix citext's upgrade-from-unpackaged script to set its collation correctly.

  3. Mark operator implementation functions as such in their comments.

  4. Add KNNGIST support to contrib/btree_gist.

  5. Fix plpython breakage detected on certain Fedora machines on buildfarm.

On Sat, Mar 5, 2011 at 8:41 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Fri, Mar 4, 2011 at 11:22 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Fri, Mar 4, 2011 at 10:44 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>>> So it seems like the only thing that is an absolute must-do is write
>>> some release notes.
>>
>> Here's a rough attempt at filtering the post-alpha3 commit log down to
>> approximately the set of things worth adding to the alpha4 release
>> notes.
>
> Working on SGML-ifying this...

OK, first attempt committed.  Proof-reading and double-checking that I
haven't left things out is very welcome.

I'm not entirely convinced the sections this is divided up into are
the best possible choices, but neither am I sure exactly what would be
better.  Suggestions welcome.

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