Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)
Jan Urbański <wulczer@wulczer.org>
From: Jan Urbański <wulczer@wulczer.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2011-03-01T20:53:46Z
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
On 01/03/11 21:35, Tom Lane wrote: > Josh Berkus <josh@agliodbs.com> writes: >> I'm ok with closing things as of the end of the 15 days, say Thursday or >> Friday. > > It might be a good idea to make a list of what we have left to do before > we can wrap an alpha. Here are some things on my list. Not all of them > are necessarily release blockers, but we need to discuss which ones are: > > * Regression test failures from recent plpython patches. These are > affecting enough machines to make them "must fix before alpha", IMO. > There are some variations in error message wording, which are not too > terrible but also not exactly hard to fix. The python assert failure > that some Fedora machines are reporting is considerably more disturbing. I'm looking into the crash, no luck so long. Jan