Project

Profile

Help

Task #7677

Release Pulp2 2.21.4

Added by ggainey about 2 months ago. Updated 26 days ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Checklist


Related issues

Copied to Pulp - Task #7801: Release Pulp2 2.21.4-2CLOSED - CURRENTRELEASE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by ggainey about 2 months ago

  • Checklist item Identify that a release needs to happen via pulp-dev. set to Done
  • Checklist item Create a Release Planning Page specific for that release. set to Done
  • Checklist item Link to the new page made in step (2) from the overall Release Schedule. set to Done
  • Checklist item Communicate the dev feeze datetime to pulp-dev with a link to the new release schedule. set to Done
  • Checklist item Make sure the version being planned has a 'Platform Release' entry in Redmine's custom field. set to Done
  • Checklist item Update the relevant Redmine filter for the next bugfix or next feature release. set to Done

#2 Updated by ggainey about 2 months ago

  • Project changed from Debian Support to Pulp

#3 Updated by ggainey about 2 months ago

  • Checklist item 24 hours (or earlier) prior to dev feeze it's good to send a reminder to pulp-dev. set to Done

#4 Updated by ggainey about 2 months ago

  • Checklist item 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. set to Done
  • Checklist item Besides sending email, after the dev freeze occurs, you need to update the Release Schedule: set to Done
  • Checklist item Release-schedule, post-freeze-email: strikethrough the dev freeze date since it occurred set to Done
  • Checklist item Release-schedule, post-freeze-email: Add a link to the redmine query for issue to be included. set to Done

#5 Updated by ggainey about 1 month ago

  • Checklist item Release-schedule, post-freeze-email: Talk with build team to update the page with a firm (not-tentative) beta date. set to Done

#6 Updated by ggainey about 1 month ago

  • Checklist item Update the docs configs in pulp/pulp 2-master branch. set to Done

#7 Updated by ggainey about 1 month ago

  • Checklist item Update each project's release notes set to Done

#8 Updated by ggainey about 1 month ago

  • Checklist item deleted (Move all of the issues from MODIFIED to ON_QA)
  • Checklist item deleted (Trigger the docs build to ensure the beta's docs are pushed to the right place)
  • Checklist item deleted (Create the beta announcements so you're ready to send them. This is a subset of the GA process. Specifically for Betas we only: (a) trigger the docs build, (b) email announce, (c) twitter announce. We do not blog post or update IRC for beta announcements.)
  • Checklist item deleted (Add the Beta to the list of Betas)
  • Checklist item deleted (Publish and send out the announcements)
  • Checklist item ack that the beta is built and ready to be published received from the build team. set to Done

#9 Updated by ggainey about 1 month ago

  • Checklist item Ask the build team to push the bits to the testing repos and wait for the to ack that they did set to Done

#10 Updated by ggainey about 1 month ago

  • Checklist item Update the docs configs in pulp/pulp 2-master branch. set to Not done

#11 Updated by ggainey about 1 month ago

  • Checklist item Strike through the Beta on the Wiki Release page and ensure that the next date (GA) is firm and accurate not tentative set to Done
  • Checklist item In case of a new Z release update that config accordingly at all stages. set to Done
  • Checklist item Ensure the correct version/release is set in the sphinx config on the release branch, e.g. 2.19-release. If it's not, talk to the build team to figure out if you should still wait or if you should change it yourself with a PR. set to Done

#12 Updated by ggainey 30 days ago

  • Checklist item On GA release day, the build team will build the final assets and work with engineering to have them tested. set to Done

#13 Updated by ggainey 30 days ago

  • Checklist item Update the docs configs in pulp/pulp 2-master branch. set to Done

#14 Updated by ggainey 30 days ago

  • Checklist item Make sure jenkins jobs are green and there are no tests failures. set to Done

#15 Updated by ggainey 29 days ago

  • Checklist item trigger a final docs build set to Done
  • Checklist item Trigger a build on this page: https://www.travis-ci.org/pulp/pulp/ set to Done

#16 Updated by ggainey 28 days ago

  • Checklist item Ensure it passes. set to Done
  • Checklist item Load https://docs.pulpproject.org/ and ensure it shows the expected new version as the home page docs. set to Done

#17 Updated by ggainey 27 days ago

  • Checklist item Email announce set to Done

#18 Updated by ggainey 27 days ago

  • Checklist item Blog announce set to Done
  • Checklist item Twitter Announce set to Done

#19 Updated by ggainey 27 days ago

  • Checklist item send the final announcements to All The Places set to Done
  • Checklist item Move issues to CLOSED - CURRENTRELEASE set to Done

#20 Updated by ggainey 27 days ago

  • Checklist item Update the Wiki Release Page set to Done
  • Checklist item Strikethrough the release date since it's completed. A completed page should be fully struckthrough like this one set to Done

#21 Updated by ggainey 26 days ago

  • Checklist item Update IRC set to Done

#22 Updated by ggainey 26 days ago

  • Status changed from ASSIGNED to CLOSED - CURRENTRELEASE

#23 Updated by ggainey 23 days ago

  • Copied to Task #7801: Release Pulp2 2.21.4-2 added

Please register to edit this issue

Also available in: Atom PDF