| 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 17:19:13 |
| Message-ID: | 3f5edde6-bd8a-d1d3-007d-7d7a715f2616@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
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.
>
> 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.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2016-10-18 20:03:24 | Re: volunteer to draft next update release |
| Previous Message | Umair Shahid | 2016-10-18 17:15:48 | Re: volunteer to draft next update release |