Jira (PDB-4393) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.4.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4393 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.4.0) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/07 3:32 PM Due Date: 2019/06/11 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-06-18) 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-4394) Bump versions, push directly, and tag (PuppetDB 6.4.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4394 Bump versions, push directly, and tag (PuppetDB 6.4.0) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/07 3:32 PM Due Date: 2019/06/14 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-06-18) (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. Perform a test promotion: With the version still a -SNAPSHOT, and all commmits merged into the release branch, attempt a test promotion by running the "manual promotion kickoff" job. This is to make sure the pipelines will work when the actual tag is promoted. 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
Jira (PDB-4396) Update winston (PuppetDB 6.4.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4396 Update winston (PuppetDB 6.4.0) Issue Type: Task Assignee: Zachary Kent Created: 2019/06/07 3:33 PM Due Date: 2019/06/19 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-06-18) 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-4395) Check builds, promote to PE (PuppetDB 6.3.3)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-4395 Check builds, promote to PE (PuppetDB 6.3.3) Change By: Nirupama Mantha Summary: Check builds, promote to PE (PuppetDB 6. 4 3 . 0 3 ) 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.311756.1559946782000.43124.1560293400970%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4396) Update winston (PuppetDB 6.3.3)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-4396 Update winston (PuppetDB 6.3.3) Change By: Nirupama Mantha Summary: Update winston (PuppetDB 6. 4 3 . 0 3 ) 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.311758.1559946798000.43120.1560293400781%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4394) Bump versions, push directly, and tag (PuppetDB 6.3.3)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-4394 Bump versions, push directly, and tag (PuppetDB 6.3.3) Change By: Nirupama Mantha Summary: Bump versions, push directly, and tag (PuppetDB 6. 4 3 . 0 3 ) 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.311755.1559946773000.43128.1560293401158%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4393) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.3)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-4393 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.3) Change By: Nirupama Mantha Summary: Reconcile git commits, JIRA tickets, and versions (PuppetDB 6. 4 3 . 0 3 ) 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.311754.1559946766000.43131.1560293460635%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4392) Merge-up, branch, and create pipelines (PuppetDB 6.3.3)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-4392 Merge-up, branch, and create pipelines (PuppetDB 6.3.3) Change By: Nirupama Mantha Summary: Merge-up, branch, and create pipelines (PuppetDB 6. 4 3 . 0 3 ) 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.311753.155994676.43136.1560293460870%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9739) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.5.0)
Title: Message Title Nirupama Mantha assigned an issue to James Shen Puppet / PUP-9739 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.5.0) Change By: Nirupama Mantha 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.311728.1559946575000.48556.1560590520448%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9739) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.5.0)
Title: Message Title Nirupama Mantha updated an issue Puppet / PUP-9739 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.5.0) Change By: Nirupama Mantha (Initial planned release date: 2019-06-18)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 proj-puppet-releases slack room for go/no-go decision.4) Send email indicating Ready To Ship milestone has been achieved. 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 (PUP-9829) Prepare JIRA and Confluence for release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9829 Prepare JIRA and Confluence for release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:22 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 and puppet-agent 6.7.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9832) Prepare release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9832 Prepare release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Bill Tang Created: 2019/07/17 2:22 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9830) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9830 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:22 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9833) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9833 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:22 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 ‘Proj-puppet-releases’ Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9831) Prepare documentation updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9831 Prepare documentation updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 2:22 PM Due Date: 2019/07/19 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9828) Puppet Platform 6.7.0 Release - 2019-07-23
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9828 Puppet Platform 6.7.0 Release - 2019-07-23 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/07/17 2:22 PM Due Date: 2019/07/23 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.7.0 Release - 2019-07-23 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9835) Send release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9835 Send release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/07/17 2:23 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 is now available".
Jira (PUP-9834) Publish documentation and updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9834 Publish documentation and updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 2:23 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9836) Update Confluence and JIRA based on release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9836 Update Confluence and JIRA based on release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:23 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 d
Jira (PUP-9837) Communicate scope and timeline of next release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9837 Communicate scope and timeline of next release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:24 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9838) Puppet Platform 6.7.0 Release - 2019-07-23
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9838 Puppet Platform 6.7.0 Release - 2019-07-23 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/07/17 2:29 PM Due Date: 2019/07/23 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.7.0 Release - 2019-07-23 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9842) Prepare release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9842 Prepare release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Bill Tang Created: 2019/07/17 2:29 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9840) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9840 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:29 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9841) Prepare documentation updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9841 Prepare documentation updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 2:29 PM Due Date: 2019/07/19 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9843) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9843 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:29 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 ‘Proj-puppet-releases’ Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9839) Prepare JIRA and Confluence for release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9839 Prepare JIRA and Confluence for release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:29 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 and puppet-agent 6.7.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9846) Update Confluence and JIRA based on release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9846 Update Confluence and JIRA based on release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:30 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 d
Jira (PUP-9845) Send release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9845 Send release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/07/17 2:30 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 is now available".
Jira (PUP-9844) Publish documentation and updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9844 Publish documentation and updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 2:30 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9847) Communicate scope and timeline of next release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9847 Communicate scope and timeline of next release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:31 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9848) Puppet Platform 6.7.0 Release - 2019-07-23
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9848 Puppet Platform 6.7.0 Release - 2019-07-23 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/07/17 3:32 PM Due Date: 2019/07/23 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.7.0 Release - 2019-07-23 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9851) Prepare documentation updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9851 Prepare documentation updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 3:32 PM Due Date: 2019/07/19 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9849) Prepare JIRA and Confluence for release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9849 Prepare JIRA and Confluence for release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:32 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 and puppet-agent 6.7.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9850) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9850 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:32 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9854) Publish documentation and updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9854 Publish documentation and updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 3:33 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9852) Prepare release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9852 Prepare release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Bill Tang Created: 2019/07/17 3:33 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9853) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9853 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:33 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 ‘Proj-puppet-releases’ Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9857) Communicate scope and timeline of next release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9857 Communicate scope and timeline of next release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:34 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9855) Send release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9855 Send release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/07/17 3:34 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 is now available".
Jira (PUP-9856) Update Confluence and JIRA based on release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9856 Update Confluence and JIRA based on release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:34 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 d
Jira (PUP-9879) Prepare JIRA and Confluence for release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9879 Prepare JIRA and Confluence for release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 6:18 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 and puppet-agent 6.7.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9878) Puppet Platform 6.7.0 Release - 2019-07-23
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9878 Puppet Platform 6.7.0 Release - 2019-07-23 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/07/17 6:18 PM Due Date: 2019/07/23 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.7.0 Release - 2019-07-23 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9880) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9880 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 6:18 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9882) Prepare release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9882 Prepare release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Bill Tang Created: 2019/07/17 6:19 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9881) Prepare documentation updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9881 Prepare documentation updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 6:19 PM Due Date: 2019/07/19 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9883) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9883 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 6:19 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 ‘Proj-puppet-releases’ Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9884) Publish documentation and updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9884 Publish documentation and updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 6:19 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9885) Send release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9885 Send release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/07/17 6:20 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 is now available".
Jira (PUP-9886) Update Confluence and JIRA based on release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9886 Update Confluence and JIRA based on release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 6:20 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 d
Jira (PUP-9887) Communicate scope and timeline of next release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9887 Communicate scope and timeline of next release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 6:20 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9888) Puppet Platform 6.7.0 Release - 2019-07-23
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9888 Puppet Platform 6.7.0 Release - 2019-07-23 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/07/17 6:41 PM Due Date: 2019/07/23 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.7.0 Release - 2019-07-23 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9890) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9890 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 6:41 PM Due Date: 2019/07/18 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9891) Prepare documentation updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9891 Prepare documentation updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 6:41 PM Due Date: 2019/07/20 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9889) Prepare JIRA and Confluence for release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9889 Prepare JIRA and Confluence for release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 6:41 PM Due Date: 2019/07/18 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 and puppet-agent 6.7.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9892) Prepare release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9892 Prepare release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Bill Tang Created: 2019/07/17 6:42 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9894) Publish documentation and updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9894 Publish documentation and updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 6:42 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9893) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9893 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 6:42 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 ‘Proj-puppet-releases’ Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9895) Send release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9895 Send release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/07/17 6:43 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 is now available".
Jira (PUP-9896) Update Confluence and JIRA based on release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9896 Update Confluence and JIRA based on release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 6:43 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 d
Jira (PUP-9897) Communicate scope and timeline of next release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9897 Communicate scope and timeline of next release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 6:43 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9902) Prepare release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha commented on PUP-9902 Re: Prepare release announcement (Puppet Platform 6.7.0) This release contains bug fixes and enhancements, notably: You can see the full list of changes in the release notes cc/Jean Bond Yasmin Rajabi 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.317016.1563415155000.27310.1563902580538%40Atlassian.JIRA.
Jira (PUP-9902) Prepare release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha commented on PUP-9902 Re: Prepare release announcement (Puppet Platform 6.7.0) This release contains bug fixes and enhancements, notably: Puppet 6.7 adds new `ca_fingerprint` setting verifies the CA bundle download against a fingerprint. The new Puppet Server 6.5 release includes an upgrade to Jetty. With this update, Puppet Server now defaults to stronger FIPS-compliant ciphers, but you must first remove the weak ciphers. We urge all Puppet Server users to update to this new version and remove the outdated cipher suite. See the Puppet Server release notes (https://puppet.com/docs/puppetserver/6.5/release_notes.html) for details. You can see the full list of changes in the release notes https://puppet.com/docs/puppet/6.7/release_notes_puppet.html cc/ Morgan Rhodes updated release notes here 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.317016.1563415155000.27681.1563912780655%40Atlassian.JIRA.
Jira (PUP-9917) Prepare JIRA and Confluence for release (Puppet Platform 6.7.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9917 Prepare JIRA and Confluence for release (Puppet Platform 6.7.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/24 4:32 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-26) 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.7.1 and puppet-agent 6.7.1 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9918) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9918 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/24 4:32 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-26) 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-9916) Puppet Platform 6.7.1 Release - 2019-07-26
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9916 Puppet Platform 6.7.1 Release - 2019-07-26 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/07/24 4:32 PM Due Date: 2019/07/26 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.7.1 Release - 2019-07-26 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9919) Prepare documentation updates and release notes (Puppet Platform 6.7.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9919 Prepare documentation updates and release notes (Puppet Platform 6.7.1) Issue Type: Task Assignee: Jean Bond Created: 2019/07/24 4:33 PM Due Date: 2019/07/26 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-26) 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-9920) Prepare release announcement (Puppet Platform 6.7.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9920 Prepare release announcement (Puppet Platform 6.7.1) Issue Type: Task Assignee: Jed Gresham Created: 2019/07/24 4:33 PM Due Date: 2019/07/25 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-26) 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-9921) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9921 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/24 4:33 PM Due Date: 2019/07/25 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-26) 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 ‘Proj-puppet-releases’ Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9922) Publish documentation and updates and release notes (Puppet Platform 6.7.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9922 Publish documentation and updates and release notes (Puppet Platform 6.7.1) Issue Type: Task Assignee: Jean Bond Created: 2019/07/24 4:33 PM Due Date: 2019/07/26 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-26) 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-9923) Send release announcement (Puppet Platform 6.7.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9923 Send release announcement (Puppet Platform 6.7.1) Issue Type: Task Assignee: Sara Meisburger Created: 2019/07/24 4:34 PM Due Date: 2019/07/26 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-26) 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.7.1 is now available".
Jira (PUP-9924) Update Confluence and JIRA based on release (Puppet Platform 6.7.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9924 Update Confluence and JIRA based on release (Puppet Platform 6.7.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/24 4:34 PM Due Date: 2019/07/27 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-26) 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 d
Jira (PUP-9925) Communicate scope and timeline of next release (Puppet Platform 6.7.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9925 Communicate scope and timeline of next release (Puppet Platform 6.7.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/24 4:34 PM Due Date: 2019/07/27 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-26) 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-9920) Prepare release announcement (Puppet Platform 6.7.1)
Title: Message Title Nirupama Mantha commented on PUP-9920 Re: Prepare release announcement (Puppet Platform 6.7.1) I think we should be able to handle this one, I'll work with Jean 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318037.156401119.30288.1564011900099%40Atlassian.JIRA.
Jira (PUP-9920) Prepare release announcement (Puppet Platform 6.7.1)
Title: Message Title Nirupama Mantha commented on PUP-9920 Re: Prepare release announcement (Puppet Platform 6.7.1) Thanks Jean Bond , do we just say we had to burn the tag for 6.7.1? If you can add the link to the release note here, I will have the final version of the notes for Sara Meisburger updated in a comment here 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318037.156401119.32011.1564096920107%40Atlassian.JIRA.
Jira (PUP-9926) "Failed to apply catalog: undefined method `each' for #"
Title: Message Title Nirupama Mantha commented on PUP-9926 Re: "Failed to apply catalog: undefined method `each' for #" Josh Cooper Gheorghe Popescu please update the ticket status 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318074.1564051611000.32158.1564100520283%40Atlassian.JIRA.
Jira (PUP-9920) Prepare release announcement (Puppet Platform 6.7.2)
Title: Message Title Nirupama Mantha updated an issue Puppet / PUP-9920 Prepare release announcement (Puppet Platform 6.7.2) Change By: Nirupama Mantha Summary: Prepare release announcement (Puppet Platform 6.7. 1 2 ) 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318037.156401119.32982.1564163760775%40Atlassian.JIRA.
Jira (PUP-9920) Prepare release announcement (Puppet Platform 6.7.2)
Title: Message Title Nirupama Mantha commented on PUP-9920 Re: Prepare release announcement (Puppet Platform 6.7.2) Thanks Jean Bond ! 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318037.156401119.32989.1564163880456%40Atlassian.JIRA.
Jira (PUP-9920) Prepare release announcement (Puppet Platform 6.7.2)
Title: Message Title Nirupama Mantha commented on PUP-9920 Re: Prepare release announcement (Puppet Platform 6.7.2) This release fixes regression errors introduced in Puppet 6.7.0: When using the `mailalias` resource type, Puppet was unable to parse certain files and returned errors. When using the `puppetlabs-ciscopuppet` module, automatic relationships, such as autorequire, could cause the catalog application to fail. Puppet 6.7.1 was never released. You can see the full list of changes in the release notes https://puppet.com/docs/puppet/6.7/release_notes_puppet.html cc Sara Meisburger Jean Bond here is the final release announcement 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318037.156401119.33003.1564164000148%40Atlassian.JIRA.
Jira (PUP-9916) Puppet Platform 6.7.2 Release - 2019-07-26
Title: Message Title Nirupama Mantha updated an issue Puppet / PUP-9916 Puppet Platform 6.7.2 Release - 2019-07-26 Change By: Nirupama Mantha Summary: Puppet Platform 6.7. 1 2 Release - 2019-07-26 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318033.1564011166000.32983.1564163760783%40Atlassian.JIRA.
Jira (PUP-9914) v6.7.0 Breaks camptocamp-postfix
Title: Message Title Nirupama Mantha updated an issue Puppet / PUP-9914 v6.7.0 Breaks camptocamp-postfix Change By: Nirupama Mantha Fix Version/s: PUP 6.7.1 Fix Version/s: PUP 6.7.2 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.317861.1563928891000.44932.1565116321019%40Atlassian.JIRA.
Jira (PUP-9948) Prepare documentation updates and release notes (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9948 Prepare documentation updates and release notes (Puppet Platform 6.8.0) Issue Type: Task Assignee: Jean Bond Created: 2019/08/08 2:57 PM Due Date: 2019/08/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-9951) Publish documentation and updates and release notes (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9951 Publish documentation and updates and release notes (Puppet Platform 6.8.0) Issue Type: Task Assignee: Jean Bond Created: 2019/08/08 2:58 PM Due Date: 2019/08/21 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-9945) Puppet Platform 6.8.0 Release - 2019-08-21
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9945 Puppet Platform 6.8.0 Release - 2019-08-21 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/08/08 2:57 PM Due Date: 2019/08/21 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.8.0 Release - 2019-08-21 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9949) Prepare release announcement (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9949 Prepare release announcement (Puppet Platform 6.8.0) Issue Type: Task Assignee: Bill Tang Created: 2019/08/08 2:57 PM Due Date: 2019/08/20 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-9950) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9950 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.8.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/08 2:57 PM Due Date: 2019/08/20 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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 ‘Proj-puppet-releases’ Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9947) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9947 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.8.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/08 2:57 PM Due Date: 2019/08/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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 Slack) 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-9946) Prepare JIRA and Confluence for release (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9946 Prepare JIRA and Confluence for release (Puppet Platform 6.8.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/08 2:57 PM Due Date: 2019/08/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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.8.0 and puppet-agent 6.8.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9952) Send release announcement (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9952 Send release announcement (Puppet Platform 6.8.0) Issue Type: Task Assignee: Sara Meisburger Created: 2019/08/08 2:58 PM Due Date: 2019/08/21 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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.8.0 is now available".
Jira (PUP-9954) Communicate scope and timeline of next release (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9954 Communicate scope and timeline of next release (Puppet Platform 6.8.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/08 2:58 PM Due Date: 2019/08/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-9953) Update Confluence and JIRA based on release (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9953 Update Confluence and JIRA based on release (Puppet Platform 6.8.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/08 2:58 PM Due Date: 2019/08/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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 d
Jira (PDB-4475) Bump versions, push directly, and tag (PuppetDB 6.5.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4475 Bump versions, push directly, and tag (PuppetDB 6.5.0) Issue Type: Task Assignee: Rob Browning Created: 2019/08/08 3:01 PM Due Date: 2019/08/16 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) (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-new' Slack channel 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-4474) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.5.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4474 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.5.0) Issue Type: Task Assignee: Rob Browning Created: 2019/08/08 3:01 PM Due Date: 2019/08/13 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-4473) Merge-up, branch, and create pipelines (PuppetDB 6.5.0)
Title: Message Title
Nirupama Mantha created an issue
PuppetDB / PDB-4473
Merge-up, branch, and create pipelines (PuppetDB 6.5.0)
Issue Type:
Task
Assignee:
Rob Browning
Created:
2019/08/08 3:01 PM
Due Date:
2019/08/13
Priority:
Normal
Reporter:
Nirupama Mantha
(Initial planned release date: 2019-08-21) 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-4476) Check builds, promote to PE (PuppetDB 6.5.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4476 Check builds, promote to PE (PuppetDB 6.5.0) Issue Type: Task Assignee: Rob Browning Created: 2019/08/08 3:01 PM Due Date: 2019/08/16 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-4477) Update winston (PuppetDB 6.5.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4477 Update winston (PuppetDB 6.5.0) Issue Type: Task Assignee: Rob Browning Created: 2019/08/08 3:01 PM Due Date: 2019/08/22 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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 (PUP-9949) Prepare release announcement (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha commented on PUP-9949 Re: Prepare release announcement (Puppet Platform 6.8.0) The next release in the Platform 6 series, Platform 6.8.0 is now available! The release contains bug fixes and minor improvements, including: Bill Tang to add list here For the full list of changes, check out the release notes: Jean Bond to add release notes link here 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.320255.1565301453000.64828.1566343620188%40Atlassian.JIRA.
Jira (PUP-9946) Prepare JIRA and Confluence for release (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha updated an issue Puppet / PUP-9946 Prepare JIRA and Confluence for release (Puppet Platform 6.8.0) Change By: Nirupama Mantha (Initial planned release date: 2019-08-21)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.8.0 and puppet-agent 6.8.0 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-9980) Prepare JIRA and Confluence for release (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9980 Prepare JIRA and Confluence for release (Puppet Platform 6.8.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/27 4:58 PM Due Date: 2019/08/27 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 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.8.1 and puppet-agent 6.8.1 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9979) Puppet Platform 6.8.1 Release - 2019-08-28
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9979 Puppet Platform 6.8.1 Release - 2019-08-28 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/08/27 4:58 PM Due Date: 2019/08/28 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.8.1 Release - 2019-08-28 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9982) Prepare documentation updates and release notes (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9982 Prepare documentation updates and release notes (Puppet Platform 6.8.1) Issue Type: Task Assignee: Jean Bond Created: 2019/08/27 4:59 PM Due Date: 2019/08/29 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 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
