Draft release notes for next week's releases

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Draft release notes for next week's releases
Date: 2016-10-21 23:51:09
Message-ID: 31882.1477093869@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I have committed draft release notes at
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=eacaf6e29fd2a3047aff9738a35a8e9b05e55375

They should be up on the website at
https://www.postgresql.org/docs/devel/static/release-9-6-1.html
as soon as guaibasaurus does its next run (about half an hour
from now, looks like).

We need to consider how to document recovery procedures for the
recently-fixed FSM and VM corruption bugs. For the moment I've
assumed that the main documentation for this will be on the wiki,
but if so, we need to put in at least placeholder pages for the
release notes to point to. (Also, somebody want to start filling
in the placeholders?)

For the moment, there are just notes for 9.6.1; I'll slice and
dice them for the back branches later. Note that quite a few
of the items don't really apply to 9.6.1 because the bug fixes
are already there in 9.6.0. This is visible in the SGML source
because the comments for them look like

Branch: REL9_6_STABLE Release: REL9_6_0 [36646d3af] 2016-09-03 13:28:53 -0400

Please review ...

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2016-10-21 23:58:29 Re: Draft release notes for next week's releases
Previous Message Peter Geoghegan 2016-10-21 23:45:52 tuplesort_gettuple_common() and *should_free argument