Jira (PUP-9776) Prepare JIRA and Confluence for release (Puppet Platform 6.4.3)
Title: Message Title Kenn Hussey assigned an issue to Kenn Hussey Puppet / PUP-9776 Prepare JIRA and Confluence for release (Puppet Platform 6.4.3) Change By: Kenn Hussey Assignee: Nirupama Mantha Kenn Hussey Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312760.1560728066000.7076.1562598960166%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9766) Prepare JIRA and Confluence for release (Puppet Platform 6.0.10)
Title: Message Title Kenn Hussey assigned an issue to Kenn Hussey Puppet / PUP-9766 Prepare JIRA and Confluence for release (Puppet Platform 6.0.10) Change By: Kenn Hussey Assignee: Nirupama Mantha Kenn Hussey Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312728.1560727454000.7071.1562598900157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9756) Prepare JIRA and Confluence for release (Puppet Platform 5.5.16)
Title: Message Title Kenn Hussey assigned an issue to Kenn Hussey Puppet / PUP-9756 Prepare JIRA and Confluence for release (Puppet Platform 5.5.16) Change By: Kenn Hussey Assignee: Nirupama Mantha Kenn Hussey Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312691.1560727096000.7073.1562598900178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9767) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.0.10)
Title: Message Title Kenn Hussey assigned an issue to James Shen Puppet / PUP-9767 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.0.10) Change By: Kenn Hussey Assignee: Nirupama Mantha James Shen Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312729.1560727461000.7015.1562593500380%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9757) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.16)
Title: Message Title Kenn Hussey assigned an issue to James Shen Puppet / PUP-9757 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.16) Change By: Kenn Hussey Assignee: Nirupama Mantha James Shen Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312692.1560727102000.7010.1562593500351%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9756) Prepare JIRA and Confluence for release (Puppet Platform 5.5.16)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9756 Prepare JIRA and Confluence for release (Puppet Platform 5.5.16) Change By: Kenn Hussey (Initial planned release date: 2019-07-16)1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release.2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments.3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA.4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it.5) Update the “master” filters for Puppet Platform 5.5. 15 16 and puppet-agent 5.5. 15 16 to reference the “Fixed in” filters created above.6) Update the community feedback filter for Puppet Platform X.y to reference the “Introduced in” filter created above. Add Comment
Jira (PUP-9756) Prepare JIRA and Confluence for release (Puppet Platform 5.5.16)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9756 Prepare JIRA and Confluence for release (Puppet Platform 5.5.16) Change By: Kenn Hussey Summary: Prepare JIRA and Confluence for release (Puppet Platform 5.5. 15 16 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312691.1560727096000.6981.1562592360295%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9761) Publish documentation and updates and release notes (Puppet Platform 5.5.16)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9761 Publish documentation and updates and release notes (Puppet Platform 5.5.16) Change By: Kenn Hussey Summary: Publish documentation and updates and release notes (Puppet Platform 5.5. 15 16 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312698.1560727142000.6970.1562592300429%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9760) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.16)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9760 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.16) Change By: Kenn Hussey Summary: Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5. 15 16 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312696.1560727129000.6972.1562592300436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9759) Prepare release announcement (Puppet Platform 5.5.16)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9759 Prepare release announcement (Puppet Platform 5.5.16) Change By: Kenn Hussey Summary: Prepare release announcement (Puppet Platform 5.5. 15 16 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312694.1560727115000.6975.1562592300446%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9758) Prepare documentation updates and release notes (Puppet Platform 5.5.16)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9758 Prepare documentation updates and release notes (Puppet Platform 5.5.16) Change By: Kenn Hussey Summary: Prepare documentation updates and release notes (Puppet Platform 5.5. 15 16 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312693.1560727109000.6977.1562592300453%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9757) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.16)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9757 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.16) Change By: Kenn Hussey Summary: Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5. 15 16 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312692.1560727102000.6979.1562592300462%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9762) Send release announcement (Puppet Platform 5.5.16)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9762 Send release announcement (Puppet Platform 5.5.16) Change By: Kenn Hussey Summary: Send release announcement (Puppet Platform 5.5. 15 16 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312702.1560727175000.6966.1562592240383%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9762) Send release announcement (Puppet Platform 5.5.16)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9762 Send release announcement (Puppet Platform 5.5.16) Change By: Kenn Hussey (Initial planned release date: 2019-07-16)Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account -* Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send.* If this release has security implications, also send to puppet-security-annou...@googlegroups.com.* Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 5.5. 15 16 is now available". Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group
Jira (PUP-9763) Update Confluence and JIRA based on release (Puppet Platform 5.5.16)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9763 Update Confluence and JIRA based on release (Puppet Platform 5.5.16) Change By: Kenn Hussey Summary: Update Confluence and JIRA based on release (Puppet Platform 5.5. 15 16 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312703.1560727182000.6964.1562592240372%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9764) Communicate scope and timeline of next release (Puppet Platform 5.5.16)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9764 Communicate scope and timeline of next release (Puppet Platform 5.5.16) Change By: Kenn Hussey Summary: Communicate scope and timeline of next release (Puppet Platform 5.5. 15 16 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312704.1560727189000.6962.1562592240362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9755) Puppet Platform 5.5.16 Release - 2019-07-16
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9755 Puppet Platform 5.5.16 Release - 2019-07-16 Change By: Kenn Hussey Puppet Platform 5.5. 15 16 Release - 2019-07-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312690.1560727093000.6951.1562592120365%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9755) Puppet Platform 5.5.16 Release - 2019-07-16
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9755 Puppet Platform 5.5.16 Release - 2019-07-16 Change By: Kenn Hussey Summary: Puppet Platform 5.5. 15 16 Release - 2019-07-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312690.1560727093000.6949.1562592120358%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9755) Puppet Platform 5.5.16 Release - 2019-07-16
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9755 Puppet Platform 5.5.16 Release - 2019-07-16 Change By: Kenn Hussey Epic Name: Puppet Platform 5.5. 15 16 Release - 2019-07-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312690.1560727093000.6953.1562592120372%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9806) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey assigned an issue to James Shen Puppet / PUP-9806 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.6.0) Change By: Kenn Hussey Assignee: Kenn Hussey James Shen Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314022.1561488088000.63925.1561659420230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9805) Prepare release announcement (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey commented on PUP-9805 Re: Prepare release announcement (Puppet Platform 6.6.0) Bill Tang do you have what you need here? It would be great to have this drafted and reviewed before end of the week. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314020.1561488075000.63418.1561643400179%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9809) Update Confluence and JIRA based on release (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9809 Update Confluence and JIRA based on release (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:42 AM Due Date: 2019/07/03 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the description
Jira (PUP-9810) Communicate scope and timeline of next release (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9810 Communicate scope and timeline of next release (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:42 AM Due Date: 2019/07/03 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 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-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-9808) Send release announcement (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9808 Send release announcement (Puppet Platform 6.6.0) Issue Type: Task Assignee: Molly Waggett Created: 2019/06/25 11:42 AM Due Date: 2019/07/02 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.6.0 is now available".
Jira (PUP-9806) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9806 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:41 AM Due Date: 2019/07/01 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9807) Publish documentation and updates and release notes (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9807 Publish documentation and updates and release notes (Puppet Platform 6.6.0) Issue Type: Task Assignee: Jean Bond Created: 2019/06/25 11:41 AM Due Date: 2019/07/02 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-9803) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9803 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:41 AM Due Date: 2019/06/26 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-9804) Prepare documentation updates and release notes (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9804 Prepare documentation updates and release notes (Puppet Platform 6.6.0) Issue Type: Task Assignee: Jean Bond Created: 2019/06/25 11:41 AM Due Date: 2019/06/28 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Add Comment
Jira (PUP-9805) Prepare release announcement (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9805 Prepare release announcement (Puppet Platform 6.6.0) Issue Type: Task Assignee: Bill Tang Created: 2019/06/25 11:41 AM Due Date: 2019/07/01 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-9802) Prepare JIRA and Confluence for release (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9802 Prepare JIRA and Confluence for release (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:40 AM Due Date: 2019/06/26 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.6.0 and puppet-agent 6.6.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to reference
Jira (PUP-9801) Puppet Platform 6.6.0 Release - 2019-07-02
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9801 Puppet Platform 6.6.0 Release - 2019-07-02 Issue Type: Epic Assignee: Kenn Hussey Created: 2019/06/25 11:40 AM Due Date: 2019/07/02 Priority: Normal Reporter: Kenn Hussey Puppet Platform 6.6.0 Release - 2019-07-02 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9800) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9800 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:37 AM Due Date: 2019/07/01 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9798) Prepare documentation updates and release notes (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9798 Prepare documentation updates and release notes (Puppet Platform 6.6.0) Issue Type: Task Assignee: Jean Bond Created: 2019/06/25 11:37 AM Due Date: 2019/06/28 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Add Comment
Jira (PUP-9796) Prepare JIRA and Confluence for release (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9796 Prepare JIRA and Confluence for release (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:37 AM Due Date: 2019/06/26 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.6.0 and puppet-agent 6.6.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to reference
Jira (PUP-9799) Prepare release announcement (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9799 Prepare release announcement (Puppet Platform 6.6.0) Issue Type: Task Assignee: Bill Tang Created: 2019/06/25 11:37 AM Due Date: 2019/07/01 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-9797) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9797 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:37 AM Due Date: 2019/06/26 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-9795) Puppet Platform 6.6.0 Release - 2019-07-02
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9795 Puppet Platform 6.6.0 Release - 2019-07-02 Issue Type: Epic Assignee: Kenn Hussey Created: 2019/06/25 11:36 AM Due Date: 2019/07/02 Priority: Normal Reporter: Kenn Hussey Puppet Platform 6.6.0 Release - 2019-07-02 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9794 Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given) Change By: Kenn Hussey Fix Version/s: PUP 6.y Fix Version/s: PUP 6.6.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313648.1561146763000.59617.1561479180799%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9790 undefined method `pip_version' with pip3 provider Change By: Kenn Hussey Fix Version/s: PUP 6.y Fix Version/s: PUP 6.6.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313529.1561106191000.59610.1561479120692%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9742) Update Confluence and JIRA based on release (Puppet Platform 6.5.0)
Title: Message Title Kenn Hussey commented on PUP-9742 Re: Update Confluence and JIRA based on release (Puppet Platform 6.5.0) James Shen as discussed, I've already taken care of #8. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311735.155994663.54161.1560982800331%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9742) Update Confluence and JIRA based on release (Puppet Platform 6.5.0)
Title: Message Title Kenn Hussey assigned an issue to James Shen James Shen are you OK with "closing out" the 6.5.0 release if I take on communication around the the next one (6.6.0)? Puppet / PUP-9742 Update Confluence and JIRA based on release (Puppet Platform 6.5.0) Change By: Kenn Hussey Assignee: Nirupama Mantha James Shen Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit
Jira (PUP-9743) Communicate scope and timeline of next release (Puppet Platform 6.5.0)
Title: Message Title Kenn Hussey assigned an issue to Kenn Hussey Puppet / PUP-9743 Communicate scope and timeline of next release (Puppet Platform 6.5.0) Change By: Kenn Hussey Assignee: Nirupama Mantha Kenn Hussey Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311736.1559946637000.52644.1560905580636%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4418) Update winston (PuppetDB 6.3.3)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-4418 Update winston (PuppetDB 6.3.3) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/16 4:38 PM Due Date: 2019/07/17 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4416) Bump versions, push directly, and tag (PuppetDB 6.3.3)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-4416 Bump versions, push directly, and tag (PuppetDB 6.3.3) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/16 4:38 PM Due Date: 2019/07/12 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release before pushing a non-snapshot version and tagging. Disable automatic promotions: Go to the CI pipeline for the version being released and select the Conditional Promotion Trigger job. Click the disable button (the job's circle indicator should be gray now). Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. Go into the 'release-new' hipchat room to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in the file 'version' and project.clj in pe-puppetdb-extensions and push directly to the branch you're releasing.
Jira (PDB-4415) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.3)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-4415 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.3) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/16 4:38 PM Due Date: 2019/07/09 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Add Comment
Jira (PDB-4417) Check builds, promote to PE (PuppetDB 6.3.3)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-4417 Check builds, promote to PE (PuppetDB 6.3.3) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/16 4:38 PM Due Date: 2019/07/13 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4414) Merge-up, branch, and create pipelines (PuppetDB 6.3.3)
Title: Message Title
Kenn Hussey created an issue
PuppetDB / PDB-4414
Merge-up, branch, and create pipelines (PuppetDB 6.3.3)
Issue Type:
Task
Assignee:
Zachary Kent
Created:
2019/06/16 4:38 PM
Due Date:
2019/07/09
Priority:
Normal
Reporter:
Kenn Hussey
(Initial planned release date: 2019-07-16) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
6.0.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Jira (PUP-9782) Send release announcement (Puppet Platform 6.4.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9782 Send release announcement (Puppet Platform 6.4.3) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/06/16 4:35 PM Due Date: 2019/07/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.4.3 is now available".
Jira (PUP-9781) Publish documentation and updates and release notes (Puppet Platform 6.4.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9781 Publish documentation and updates and release notes (Puppet Platform 6.4.3) Issue Type: Task Assignee: Jean Bond Created: 2019/06/16 4:35 PM Due Date: 2019/07/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-9783) Update Confluence and JIRA based on release (Puppet Platform 6.4.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9783 Update Confluence and JIRA based on release (Puppet Platform 6.4.3) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:35 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the
Jira (PUP-9784) Communicate scope and timeline of next release (Puppet Platform 6.4.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9784 Communicate scope and timeline of next release (Puppet Platform 6.4.3) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:35 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 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-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-9777) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9777 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.3) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:34 PM Due Date: 2019/07/10 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-9775) Puppet Platform 6.4.3 Release - 2019-07-16
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9775 Puppet Platform 6.4.3 Release - 2019-07-16 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/06/16 4:34 PM Due Date: 2019/07/16 Priority: Normal Reporter: Kenn Hussey Puppet Platform 6.4.3 Release - 2019-07-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9776) Prepare JIRA and Confluence for release (Puppet Platform 6.4.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9776 Prepare JIRA and Confluence for release (Puppet Platform 6.4.3) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:34 PM Due Date: 2019/07/10 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.4.3 and puppet-agent 6.4.3 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9779) Prepare release announcement (Puppet Platform 6.4.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9779 Prepare release announcement (Puppet Platform 6.4.3) Issue Type: Task Assignee: Bill Tang Created: 2019/06/16 4:34 PM Due Date: 2019/07/15 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-9778) Prepare documentation updates and release notes (Puppet Platform 6.4.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9778 Prepare documentation updates and release notes (Puppet Platform 6.4.3) Issue Type: Task Assignee: Jean Bond Created: 2019/06/16 4:34 PM Due Date: 2019/07/12 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Add Comment
Jira (PUP-9780) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9780 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.3) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:35 PM Due Date: 2019/07/15 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PDB-4409) Merge-up, branch, and create pipelines (PuppetDB 6.0.4)
Title: Message Title
Kenn Hussey created an issue
PuppetDB / PDB-4409
Merge-up, branch, and create pipelines (PuppetDB 6.0.4)
Issue Type:
Task
Assignee:
Zachary Kent
Created:
2019/06/16 4:27 PM
Due Date:
2019/07/09
Priority:
Normal
Reporter:
Kenn Hussey
(Initial planned release date: 2019-07-16) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
6.0.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Jira (PDB-4413) Update winston (PuppetDB 6.0.4)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-4413 Update winston (PuppetDB 6.0.4) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/16 4:27 PM Due Date: 2019/07/17 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4410) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.0.4)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-4410 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.0.4) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/16 4:27 PM Due Date: 2019/07/09 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Add Comment
Jira (PDB-4412) Check builds, promote to PE (PuppetDB 6.0.4)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-4412 Check builds, promote to PE (PuppetDB 6.0.4) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/16 4:27 PM Due Date: 2019/07/13 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4411) Bump versions, push directly, and tag (PuppetDB 6.0.4)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-4411 Bump versions, push directly, and tag (PuppetDB 6.0.4) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/16 4:27 PM Due Date: 2019/07/12 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release before pushing a non-snapshot version and tagging. Disable automatic promotions: Go to the CI pipeline for the version being released and select the Conditional Promotion Trigger job. Click the disable button (the job's circle indicator should be gray now). Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. Go into the 'release-new' hipchat room to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in the file 'version' and project.clj in pe-puppetdb-extensions and push directly to the branch you're releasing.
Jira (PUP-9772) Send release announcement (Puppet Platform 6.0.10)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9772 Send release announcement (Puppet Platform 6.0.10) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/06/16 4:25 PM Due Date: 2019/07/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.0.10 is now available".
Jira (PUP-9774) Communicate scope and timeline of next release (Puppet Platform 6.0.10)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9774 Communicate scope and timeline of next release (Puppet Platform 6.0.10) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:25 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 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-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-9773) Update Confluence and JIRA based on release (Puppet Platform 6.0.10)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9773 Update Confluence and JIRA based on release (Puppet Platform 6.0.10) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:25 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the
Jira (PUP-9770) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.0.10)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9770 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.0.10) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:24 PM Due Date: 2019/07/15 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9766) Prepare JIRA and Confluence for release (Puppet Platform 6.0.10)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9766 Prepare JIRA and Confluence for release (Puppet Platform 6.0.10) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:24 PM Due Date: 2019/07/10 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.0.10 and puppet-agent 6.0.10 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9771) Publish documentation and updates and release notes (Puppet Platform 6.0.10)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9771 Publish documentation and updates and release notes (Puppet Platform 6.0.10) Issue Type: Task Assignee: Jean Bond Created: 2019/06/16 4:25 PM Due Date: 2019/07/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-9765) Puppet Platform 6.0.10 Release - 2019-07-16
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9765 Puppet Platform 6.0.10 Release - 2019-07-16 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/06/16 4:24 PM Due Date: 2019/07/16 Priority: Normal Reporter: Kenn Hussey Puppet Platform 6.0.10 Release - 2019-07-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9768) Prepare documentation updates and release notes (Puppet Platform 6.0.10)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9768 Prepare documentation updates and release notes (Puppet Platform 6.0.10) Issue Type: Task Assignee: Jean Bond Created: 2019/06/16 4:24 PM Due Date: 2019/07/12 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Add Comment
Jira (PUP-9767) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.0.10)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9767 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.0.10) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:24 PM Due Date: 2019/07/10 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-9769) Prepare release announcement (Puppet Platform 6.0.10)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9769 Prepare release announcement (Puppet Platform 6.0.10) Issue Type: Task Assignee: Bill Tang Created: 2019/06/16 4:24 PM Due Date: 2019/07/15 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PDB-4407) Check builds, promote to PE (PuppetDB 5.2.9)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-4407 Check builds, promote to PE (PuppetDB 5.2.9) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/16 4:22 PM Due Date: 2019/07/13 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4408) Update winston (PuppetDB 5.2.9)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-4408 Update winston (PuppetDB 5.2.9) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/16 4:22 PM Due Date: 2019/07/17 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4404) Merge-up, branch, and create pipelines (PuppetDB 5.2.9)
Title: Message Title
Kenn Hussey created an issue
PuppetDB / PDB-4404
Merge-up, branch, and create pipelines (PuppetDB 5.2.9)
Issue Type:
Task
Assignee:
Zachary Kent
Created:
2019/06/16 4:21 PM
Due Date:
2019/07/09
Priority:
Normal
Reporter:
Kenn Hussey
(Initial planned release date: 2019-07-16) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
6.0.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Jira (PDB-4405) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.9)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-4405 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.9) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/16 4:21 PM Due Date: 2019/07/09 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Add Comment
Jira (PDB-4406) Bump versions, push directly, and tag (PuppetDB 5.2.9)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-4406 Bump versions, push directly, and tag (PuppetDB 5.2.9) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/16 4:22 PM Due Date: 2019/07/12 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release before pushing a non-snapshot version and tagging. Disable automatic promotions: Go to the CI pipeline for the version being released and select the Conditional Promotion Trigger job. Click the disable button (the job's circle indicator should be gray now). Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. Go into the 'release-new' hipchat room to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in the file 'version' and project.clj in pe-puppetdb-extensions and push directly to the branch you're releasing.
Jira (PUP-9762) Send release announcement (Puppet Platform 5.5.15)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9762 Send release announcement (Puppet Platform 5.5.15) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/06/16 4:19 PM Due Date: 2019/07/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 5.5.15 is now available".
Jira (PUP-9755) Puppet Platform 5.5.15 Release - 2019-07-16
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9755 Puppet Platform 5.5.15 Release - 2019-07-16 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/06/16 4:18 PM Due Date: 2019/07/16 Priority: Normal Reporter: Kenn Hussey Puppet Platform 5.5.15 Release - 2019-07-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9759) Prepare release announcement (Puppet Platform 5.5.15)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9759 Prepare release announcement (Puppet Platform 5.5.15) Issue Type: Task Assignee: Bill Tang Created: 2019/06/16 4:18 PM Due Date: 2019/07/15 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-9763) Update Confluence and JIRA based on release (Puppet Platform 5.5.15)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9763 Update Confluence and JIRA based on release (Puppet Platform 5.5.15) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:19 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the
Jira (PUP-9764) Communicate scope and timeline of next release (Puppet Platform 5.5.15)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9764 Communicate scope and timeline of next release (Puppet Platform 5.5.15) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:19 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 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-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-9756) Prepare JIRA and Confluence for release (Puppet Platform 5.5.15)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9756 Prepare JIRA and Confluence for release (Puppet Platform 5.5.15) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:18 PM Due Date: 2019/07/10 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 5.5.15 and puppet-agent 5.5.15 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9760) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.15)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9760 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.15) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:18 PM Due Date: 2019/07/15 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9758) Prepare documentation updates and release notes (Puppet Platform 5.5.15)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9758 Prepare documentation updates and release notes (Puppet Platform 5.5.15) Issue Type: Task Assignee: Jean Bond Created: 2019/06/16 4:18 PM Due Date: 2019/07/12 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Add Comment
Jira (PUP-9761) Publish documentation and updates and release notes (Puppet Platform 5.5.15)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9761 Publish documentation and updates and release notes (Puppet Platform 5.5.15) Issue Type: Task Assignee: Jean Bond Created: 2019/06/16 4:19 PM Due Date: 2019/07/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-9757) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.15)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9757 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.15) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/06/16 4:18 PM Due Date: 2019/07/10 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-16) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-9599) Communicate scope and timeline of next release (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9599 Communicate scope and timeline of next release (Puppet Platform 5.5.13) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/02 10:55 AM Due Date: 2019/04/17 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) 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-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-9597) Send release announcement (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9597 Send release announcement (Puppet Platform 5.5.13) Issue Type: Task Assignee: Eric Griswold Created: 2019/04/02 10:55 AM Due Date: 2019/04/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 5.5.13 is now available".
Jira (PUP-9598) Update Confluence and JIRA based on release (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9598 Update Confluence and JIRA based on release (Puppet Platform 5.5.13) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/02 10:55 AM Due Date: 2019/04/17 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the
Jira (PUP-9595) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9595 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.13) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/02 10:54 AM Due Date: 2019/04/15 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9594) Prepare release announcement (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9594 Prepare release announcement (Puppet Platform 5.5.13) Issue Type: Task Assignee: Bill Tang Created: 2019/04/02 10:54 AM Due Date: 2019/04/15 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-9596) Publish documentation and updates and release notes (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9596 Publish documentation and updates and release notes (Puppet Platform 5.5.13) Issue Type: Task Assignee: Jean Bond Created: 2019/04/02 10:54 AM Due Date: 2019/04/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) Merge the PR linked by Jean Bond. This kicks off a build to publish the docs, which takes some time. Add Comment
Jira (PUP-9592) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9592 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.13) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/02 10:54 AM Due Date: 2019/04/10 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-9593) Prepare documentation updates and release notes (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9593 Prepare documentation updates and release notes (Puppet Platform 5.5.13) Issue Type: Task Assignee: Jean Bond Created: 2019/04/02 10:54 AM Due Date: 2019/04/12 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Add Comment
Jira (PUP-9591) Prepare JIRA and Confluence for release (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9591 Prepare JIRA and Confluence for release (Puppet Platform 5.5.13) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/02 10:53 AM Due Date: 2019/04/10 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 5.5.13 and puppet-agent 5.5.13 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9590) Puppet Platform 5.5.13 Release - 2019-04-16
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9590 Puppet Platform 5.5.13 Release - 2019-04-16 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/04/02 10:53 AM Due Date: 2019/04/16 Priority: Normal Reporter: Kenn Hussey Puppet Platform 5.5.13 Release - 2019-04-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9494) Update HA Documentation on enabling a replica
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9494 Update HA Documentation on enabling a replica Change By: Kenn Hussey Fix Version/s: PUP 6.4.0 Fix Version/s: PUP 6.4.1 Fix Version/s: PUP 6.0.8 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9542) Communicate scope and timeline of next release (Puppet Platform 6.0.7)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9542 Communicate scope and timeline of next release (Puppet Platform 6.0.7) Change By: Kenn Hussey Attachment: 6.0.8 milestones.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9542) Communicate scope and timeline of next release (Puppet Platform 6.0.7)
Title: Message Title Kenn Hussey commented on PUP-9542 Re: Communicate scope and timeline of next release (Puppet Platform 6.0.7) This is for a 6.0.8 release. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
