Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)
David Wheeler <david@kineticode.com>
From: "David E. Wheeler" <david@kineticode.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2011-03-05T22:20:37Z
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 Mar 4, 2011, at 7:44 PM, Robert Haas wrote: > So it seems like the only thing that is an absolute must-do is write > some release notes. What about this? > Yeah, the real problem in my mind is not so much citext as whether the > current representation of a type's collation property is sane in the > first place. Once we've thrashed that out, I'll be happy with a simple > "UPDATE pg_type" kluge in the citext upgrade script. Doing anything > cleaner-looking than that is a future project (and might never happen, > seeing that we've never felt a need for ALTER TYPE commands for other > properties of a basic type). > > So really I guess the release-blocker issue is > > http://archives.postgresql.org/message-id/27152(dot)1299015062(at)sss(dot)pgh(dot)pa(dot)us Best, David