Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-8431

Communicate scope and timeline of next release (Puppet Platform 5.4.0)


    • Type: Task
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • QA Risk Assessment:
      Needs Assessment


      (Initial planned release date: 2018-02-13)

      1. Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group.

      2. Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues.

      3. Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”.

      4. Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed.

      5. Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages.

      6. Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page.

      7. Send an email to stakeholders (e.g., puppet-dev@googlegroups.com and discuss-platform@puppet.com) outlining the scope and timeline for the release.






              • Assignee:
                kenn Kenn Hussey
                molly.waggett Molly Waggett
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Due: