Re: volunteer to draft next update release

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
Cc: Umair Shahid <umair(dot)shahid(at)gmail(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: volunteer to draft next update release
Date: 2016-10-18 20:03:24
Message-ID: f6949557-39a3-19a2-78fe-58852989da7f@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On 10/18/2016 10:19 AM, Josh Berkus wrote:
> On 10/18/2016 10:15 AM, Jonathan S. Katz wrote:
>> Hi Josh,
>>> On Oct 17, 2016, at 5:28 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>>>
>>> Josh, Jon, Umair:
>>>
>>> I have prepped this for you folks.
>>>
>>> https://wiki.postgresql.org/wiki/UpdateReleaseDrafting
>>>
>>> Also, I've added an archive of past update releases, as well as
>>> templates for future releases, to the "press" repository on
>>> git.postgresql.org. Let me know if any of you need permissions on that
>>> repo.
>>>
>>> This release is a bugfix release with no security issues, which is why
>>> it's a good one to start with.
>>
>> Thank you for putting this together, it is super helpful.

I thought templates + documentation would be much better than talking
just one person through it.

>>
>> Where is the starting point for compiling information about what is going into the release, i.e. the “1 to 2 weeks out” step in the guide?
>
> That's where we are now. Tarballs will be bundled on Monday.

Oh, also: 9.1 is EOL as of this release.

There are several big fixes in this release, including a data-corruption
one for 9.6.

--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Jonathan S. Katz 2016-10-18 21:50:52 Re: volunteer to draft next update release
Previous Message Josh Berkus 2016-10-18 17:19:13 Re: volunteer to draft next update release