[PDB-3568] PuppetDB 5.0.0 2017-06-27 Release Created: 2017/06/20  Updated: 2018/09/18  Resolved: 2017/07/21

Status: Closed
Project: PuppetDB
Component/s: None
Affects Version/s: None
Fix Version/s: PDB 5.0.1

Type: Task Priority: Normal
Reporter: Rob Browning Assignee: Rob Browning
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
PDB-3569 Is the code ready for release? (PDB 5... Sub-task Closed Rob Browning  
PDB-3570 Reconcile git commits and JIRA ticket... Sub-task Closed Rob Browning  
PDB-3571 Update version number in source (PDB ... Sub-task Closed Rob Browning  
PDB-3572 Merge master into stable (PDB 5.0.0) Sub-task Closed Rob Browning  
PDB-3573 Is the Jira tidy-up done for this rel... Sub-task Closed Rob Browning  
PDB-3574 Prepare long form release notes and s... Sub-task Closed Rob Browning  
PDB-3575 Tag the release and create packages (... Sub-task Closed Melissa Stone  
PDB-3576 Smoke test packages (PDB 5.0.0) Sub-task Closed Russell Mull  
PDB-3577 Go/no-go meeting (before noon PST) (P... Sub-task Closed Rob Browning  
PDB-3578 Push tag (PDB 5.0.0) Sub-task Closed Melissa Stone  
PDB-3579 Packages pushed (PDB 5.0.0) Sub-task Closed Melissa Stone  
PDB-3580 Docs pushed (PDB 5.0.0) Sub-task Closed  
PDB-3581 Send out announcements (PDB 5.0.0) Sub-task Closed Eric Sorenson  
PDB-3582 Update dujour to notify users to use ... Sub-task Closed Rob Browning  
PDB-3583 Close all resolved tickets in Jira (P... Sub-task Closed Rob Browning  
Team: Data Platform
Sprint: Hopper/Triage
Release Notes: Not Needed
QA Risk Assessment: Needs Assessment


PuppetDB 5.0.0 2017-06-27 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.

Comment by Kenn Hussey [ 2017/07/20 ]

Rob Browning can this be resolved now?

Generated at Sat Aug 08 17:50:03 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.