Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-1423 puppetserver 2.5.0 2016-08-08 Release
  3. SERVER-1428

Is the Jira tidy-up done for this release and prepared for the next one? (SERVER 2.5.0)

    XMLWordPrintable

    Details

    • Type: Sub-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:
    • Sprint:
      Server Emerald 2016-07-27, Server Emerald 2016-08-10, Server Emerald 2016-08-24
    • Release Notes:
      Not Needed

      Description

      (Initial planned release date: 2016-08-08)

      This happens on Jira - we need to clean up the current release and prepare for the next release.

      • Mark the version that's going out as "Released" in the Project Admin -> Versions panel.
      • Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future)
      • Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket):
      • 'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone
      • 'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for Everyone

        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