Re: wrapping up this CommitFest (was Re: knngist - 0.8)
Josh Berkus <josh@agliodbs.com>
From: Josh Berkus <josh@agliodbs.com>
To: pgsql-hackers@postgresql.org
Date: 2011-03-01T19:12:49Z
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 →
-
Further refine patch for commenting operator implementation functions.
- 908ab8028640 9.1.0 cited
-
Fix citext's upgrade-from-unpackaged script to set its collation correctly.
- 94be9e3f0ca9 9.1.0 cited
-
Mark operator implementation functions as such in their comments.
- 94133a935414 9.1.0 cited
-
Add KNNGIST support to contrib/btree_gist.
- 8436489c81c2 9.1.0 cited
-
Fix plpython breakage detected on certain Fedora machines on buildfarm.
- 4c966d920fb7 9.1.0 cited
>> Since we appear to be still holding the commitfest open for Sync Rep,
>> I guess this ought to get reviewed.
>
> Or else we should close the CommitFest and cut alpha4. Anyone have an
> opinion on which way to go?
I think we can give Sync Rep until the 15th, given the pace of work on
it. It is a major feature, and a complicated one.
We could even cut a pre-synch-rep Alpha4 *now*, and follow that with a
post-synch-rep Alpha5 sometime around April 1.
That'll put us in a good position for beta, and also to see what
specific issue SynR adds.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com