Project

Profile

Help

Actions

Pulp 2 Release Planning » History » Revision 2

« Previous | Revision 2/28 (diff) | Next »
bmbouter, 02/28/2018 10:18 PM
Updated with info about the dev freeze process.


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.

5. Edit the existing Redmine filter for the next bugfix or next feature release. These queries are important as they show the set of issues for the upcoming release.

Dev Freeze

To coordinate the dev freeze you should send 2 emails to the pulp-dev list.

1. 24 hours (or earlier) prior to dev feeze it's good to send a reminder to pulp-dev. Here is an example
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 This email serves also to notify release engineering and QE that development is done for that release and those are the issues.

Besides sending email, after the dev freeze occurs, you need to update the Release Schedule in two ways.

1. strikethrough the dev freeze date since it occurred
2. Talk with pcreech or @ehelms to update the page with a firm (not-tentative) beta date.

Updated by bmbouter over 6 years ago · 2 revisions