Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-1672

puppetserver 2.7.2 2016-12-06 Release


    • Type: Task
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • Team:
      Next Generation
    • Story Points:
    • 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.




            • Assignee:
              justin Justin Stoller
              jeremy.barlow Jeremy Barlow
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created:

                Zendesk Support