Horton

Re: Draft release notes complete

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Andrew Dunstan <andrew@dunslane.net>
Date: 2012-05-10T15:34:34Z
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. Expose track_iotiming information via pg_stat_statements.

  2. Rewrite GiST support code for rangetypes.

  3. Clean up a couple of box gist helper functions.

  4. Replace the "New Linear" GiST split algorithm for boxes and points with a

On Thu, May 10, 2012 at 05:31:15PM +0200, Magnus Hagander wrote:
> > I use the doc build to show patch submitters what their final work looks
> > like, and anything more than a few minutes delay makes that useless.
> >
> 
> Anything that runs off the main git repo would be useless there, since it would
> never show up prior to commit.

I will commit something then send them a URL saying, "Hey, committed,
look here for the results."

> If people want the main docs building more often that's not really a problem
> other than time - we just need to decouple it from the buildfarm and run a
> separate job for it. It's not rocket science..

I do think we need to do that.  The release note publication was stalled
for 90 minutes just in this one case.  The docs are still hard enough to
build that I can imagine others would like to have quick feedback.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +