[SERVER-1672] puppetserver 2.7.2 2016-12-06 Release Created: 2016/11/29  Updated: 2016/12/06  Resolved: 2016/12/06

Status: Resolved
Project: Puppet Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: Jeremy Barlow Assignee: Justin Stoller
Resolution: Fixed Votes: 0
Labels: maintenance
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

SERVER-1673 Is the code ready for release? (SERVE... Sub-task Resolved Justin Stoller  
SERVER-1674 Reconcile git commits and JIRA ticket... Sub-task Resolved Justin Stoller  
SERVER-1675 Update version number in source (SERV... Sub-task Resolved Justin Stoller  
SERVER-1676 Merge master into stable (SERVER 2.7.2) Sub-task Closed Justin Stoller  
SERVER-1677 Is the Jira tidy-up done for this rel... Sub-task Resolved Justin Stoller  
SERVER-1678 Prepare long form release notes and s... Sub-task Resolved  
SERVER-1679 Tag the release and create packages (... Sub-task Resolved Melissa Stone  
SERVER-1680 Smoke test packages (SERVER 2.7.2) Sub-task Resolved Justin Stoller  
SERVER-1681 Go/no-go meeting (before noon PST) (S... Sub-task Resolved Jeremy Barlow  
SERVER-1682 Push tag (SERVER 2.7.2) Sub-task Resolved Melissa Stone  
SERVER-1683 Packages pushed (SERVER 2.7.2) Sub-task Resolved Melissa Stone  
SERVER-1684 Docs pushed (SERVER 2.7.2) Sub-task Resolved Garrett Guillotte  
SERVER-1685 Send out announcements (SERVER 2.7.2) Sub-task Resolved Justin Stoller  
SERVER-1686 Update dujour to notify users to use ... Sub-task Resolved Justin Stoller  
SERVER-1687 Close all resolved tickets in Jira (S... Sub-task Resolved Justin Stoller  
Team: Next Generation
Story Points: 3
Sprint: NG 2016-12-14
QA Risk Assessment: Needs Assessment


puppetserver 2.7.2 2016-12-06 Release

When working through this ticket, add it to the board and then keep it in the Ready for Engineering column.
Move the subtasks to In Progress when you are working on them and Resolved when you have completed them.
In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items.

  • The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them.
  • Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward.
  • When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.

Generated at Mon Jan 20 08:02:23 PST 2020 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.