Pulp 2 Release Planning » History » Revision 3
Revision 2 (bmbouter, 02/28/2018 10:18 PM) → Revision 3/28 (bmbouter, 02/28/2018 11:10 PM)
# 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](https://pulp.plan.io/projects/pulp/wiki/2153_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](https://pulp.plan.io/projects/pulp/wiki/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](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.
### 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](https://www.redhat.com/archives/pulp-dev/2018-February/msg00027.html)
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.
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.
### GA Release Announcing
On GA release day, the build team will build the final assets and work with QE to have them tested. Once they are ready a developer can send the final announcements. There are three announcements: email, blog, and twitter. For the blog you'll need merge rights to the [github.com/pulp/pulpproject.org/](https://github.com/pulp/pulpproject.org/) repo. For twitter, you'll need the pulpproj twitter credentials, or know someone who can post.
#### Email announce
Use the [community_announce.py](https://github.com/bmbouter/pulp_community_tools/blob/master/release_announce.py) tool to produce the email. Send this email to pulp-list
#### Blog announce
The same tool above produces a blog post. Post it using these instructions:
1\. Make a new .md file in the [\_posts](https://github.com/pulp/pulpproject.org/tree/gh-pages/\_posts) directory that is dated and named appropriately. e.g. 2018-02-27-pulp-2.15.2-generally-available.md
2\. Push a PR with that file and merge it yourself or ask someone in #pulp-dev to merge it. The blog posts do not require review. It should show up on pulpproject.org within a few minutes after you merge it.
#### Twitter Announce
Post on twitter. Feel free to personalize it, but the announce tool also produces a generic tweet for you.
1\. Get the tweet content from the announce tool
2\. Add the link to the blog post on the end
3\. Post to twitter as @pulpproj
#### Update IRC
1\. Become operator in #pulp with: /msg ChanServ op #pulp
2\. Post your content by running something like: /topic http://pulpproject.org/ | Current Release: Pulp 2.15.2 | To report a bug: https://pulp.plan.io/projects/pulp/issues/new | Development chat: #pulp-dev | 2.15.2 Generally Available!
3\. Take away your op priviledges with: /msg ChanServ op #pulp -username where username is your irc nick, e.g. bmbouter.
.