Project

Profile

Help

Task #8085

Release Pulp2 2.21.5

Added by ggainey 12 days ago.

Status:
NEW
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 from Pulp - Task #7677: Release Pulp2 2.21.4CLOSED - CURRENTRELEASE

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

History

#1 Updated by ggainey 12 days ago

  • Copied from Task #7677: Release Pulp2 2.21.4 added

#2 Updated by ggainey 12 days ago

  • Checklist item Create a Release Planning Page specific for that release. set to Done

#3 Updated by ggainey 12 days ago

  • Checklist item Identify that a release needs to happen via pulp-dev. set to Done
  • Checklist item Link to the new page made in step (2) from the overall Release Schedule. set to Done

#4 Updated by ggainey 12 days ago

  • 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

#5 Updated by ggainey 11 days ago

  • Checklist item 24 hours (or earlier) prior to dev feeze it's good to send a reminder to pulp-dev. set to Done
  • 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

#6 Updated by ggainey 11 days ago

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

#7 Updated by ggainey 7 days ago

  • Checklist item Release-schedule, post-freeze-email: Add a link to the redmine query for issue to be included. set to Done

#8 Updated by ggainey 6 days ago

  • 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: Talk with build team to update the page with a firm (not-tentative) beta date. set to Done
  • Checklist item ack that the beta is built and ready to be published received from the build team. set to Done
  • 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
  • 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

Please register to edit this issue

Also available in: Atom PDF