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:52:08Z
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
> As I understand it, it requires only the steps described here:
>
> http://wiki.postgresql.org/wiki/Alpha_release_process
>
> That all looks pretty straightforward, assuming you can log into
> developer.postgresql.org, which I can't. I think I remember having an
> ftp account at some point, but it's not accepting connections on port
> 22, so there is doubtless some secret sauce I am missing here.
Ideally, we want to have some binaries/packages for the "final alpha".
Those broaden testing considerably.
We don't need them for all platforms, of course. Really, the critical
ones for testing are Windows and OSX. Linux/BSD/Solaris users are
pretty good at make/make install.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com