| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| 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 15:15:31 |
| Message-ID: | E405250D-BE36-4A40-A2DD-520EE611C2BA@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
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?
Thanks,
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Umair Shahid | 2016-10-18 17:15:48 | Re: volunteer to draft next update release |
| Previous Message | Josh Berkus | 2016-10-17 21:28:08 | Re: volunteer to draft next update release |