Pulp 2 Release Planning¶

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.

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.

2. Create a Release Planning Page specific for that release. For example here is the 2.15.3 release Status page. At a minimum it should contain the following:

• dev freeze date
• tentative beta date
• tentative RC date (only for Y releases, not Z releases)
• tentative GA date

3. Link to the new page made in step (2) from the overall Release Schedule.

4. Communicate the dev feeze datetime to pulp-dev with a link to the new release schedule.