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

puppetserver 2.5.0 2016-08-08 Release

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: SERVER 2.5.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      Hide

      N/a, not code

      Show
      N/a, not code
    • Sub-team:
    • Story Points:
      5
    • Sprint:
      Server Emerald 2016-07-27, Server Emerald 2016-08-10, Server Emerald 2016-08-24
    • Release Notes:
      Not Needed

      Description

      Below this line was generated by Rake, and the subtasks are confusing as they seem to be written for an Agent release. How to interpret everything and do a release for Puppet Server is documented here: https://confluence.puppetlabs.com/display/ENG/Releasing+a+new+version+of+Puppet+Server

      -------------------------------------------
      puppetserver 2.5.0 2016-08-08 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.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            chris Chris Price
            QA Contact:
            Erik Dasher
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support