Pulp 2 Release Planning » History » Sprint/Milestone 1
bmbouter, 02/26/2018 08:23 PM
Initial content
| 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. |
.