Horton

Re: wrapping up this CommitFest (was Re: knngist - 0.8)

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2011-03-01T19:48:36Z
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 Tue, Mar 1, 2011 at 2:38 PM, Magnus Hagander <magnus@hagander.net> wrote:
>> Frankly, I think we should be aiming to get a beta out in April, not
>> another alpha.
>
> That would be good, but in order to get there, +1 for cutting a new
> alpha even if syncrep isn't ready for it yet. That way we can at least
> get some more testing on all the non-syncrep code.
>
> That is assuming that cutting an alpha release isn't all that much
> work, but IIRC it's not. (Hey, I know it's not much work for me, but
> someone who actually does the work should comment on the total
> amount...)

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.

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