Pulp 2 Release Planning » History » Sprint/Milestone 2
bmbouter, 02/28/2018 10:18 PM
Updated with info about the dev freeze process.
| 1 | 1 | bmbouter | # Pulp 2 Release Planning |
|---|---|---|---|
| 2 | |||
| 3 | This serves as a step-by-step guide to coordinating a Pulp 2 release. This is mostly about facilitating the required communication to keep everyone on the same page. |
||
| 4 | |||
| 5 | 1\. Identify that a release needs to happen via pulp-dev. This can be something that is requested by anyone who wants to release bits that have been merged. |
||
| 6 | |||
| 7 | 2\. Create a Release Planning Page specific for that release. For example here is the [2.15.3 release Status](https://pulp.plan.io/projects/pulp/wiki/2153_Release_Status) page. At a minimum it should contain the following: |
||
| 8 | |||
| 9 | - dev freeze date |
||
| 10 | - tentative beta date |
||
| 11 | - tentative RC date (only for Y releases, not Z releases) |
||
| 12 | - tentative GA date |
||
| 13 | |||
| 14 | 3\. Link to the new page made in step (2) from the overall [Release Schedule](https://pulp.plan.io/projects/pulp/wiki/Release_Schedule). |
||
| 15 | |||
| 16 | 4\. Communicate the dev feeze datetime to pulp-dev with a link to the new release schedule. |
||
| 17 | 2 | bmbouter | |
| 18 | 5\. Edit the existing Redmine filter for the [next bugfix](https://pulp.plan.io/projects/pulp/issues?query_id=59) or [next feature](https://pulp.plan.io/projects/pulp/issues?query_id=61) release. These queries are important as they show the set of issues for the upcoming release. |
||
| 19 | |||
| 20 | ### Dev Freeze |
||
| 21 | |||
| 22 | To coordinate the dev freeze you should send 2 emails to the pulp-dev list. |
||
| 23 | |||
| 24 | 1\. 24 hours (or earlier) prior to dev feeze it's good to send a reminder to pulp-dev. Here is [an example](https://www.redhat.com/archives/pulp-dev/2018-February/msg00027.html) |
||
| 25 | 2\. After the freeze is done you should send an email with a link to the Redmine query showing the list of fixes and features in that release. Here is [an example](https://www.redhat.com/archives/pulp-dev/2018-February/msg00042.html) This email serves also to notify release engineering and QE that development is done for that release and those are the issues. |
||
| 26 | |||
| 27 | Besides sending email, after the dev freeze occurs, you need to update the Release Schedule in two ways. |
||
| 28 | |||
| 29 | 1\. strikethrough the dev freeze date since it occurred |
||
| 30 | 2\. Talk with @pcreech or @ehelms to update the page with a firm (not-tentative) beta date. |
.