Jira (PUP-10085) Prepare release announcement (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha commented on PUP-10085 Re: Prepare release announcement (Puppet Platform 6.10.1) The next point release in the Puppet 6 series, Puppet 6.10.1 is now available! The release contains bug fixes and minor improvements, including: Module installation performance with minitar improved Automatic (delayed start) is now an option for Windows services Module repository credentials redacted during installation Sensitive values redacted in notify resource messages This version upgrades the Ruby version to 2.5.7 This version upgrades OpenSSL to 1.1.1d This version includes a security update to curl 7.66.0 For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/latest/release_notes_puppet.html cc/Jean Bond to review, once Jean is good, Molly Waggett we should be good to send it. 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
Jira (PUP-10074) Prepare release announcement (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha commented on PUP-10074 Re: Prepare release announcement (Puppet Platform 6.4.4) The next point release in the Puppet 6.4 series, Puppet 6.4.4 is now available! The release contains bug fixes and minor improvements, including: New no_proxy setting available in puppet.conf serverip6 fact added puppet plugin information is now included in help Module installation performance with minitar improved Automatic (delayed start) is now an option for Windows services Agents now connect directly if target host is set to NO_PROXY Query parameters for HTTP and HTTPS file resources are preserved This version upgrades the Ruby version to 2.5.7 This version upgrades OpenSSL to 1.1.1d This version includes a security update to curl 7.66.0 For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/6.4/release_notes_puppet.html cc/Jean Bond to review, once Jean is good, Molly Waggett we should be good to send it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10064) Prepare release announcement (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha commented on PUP-10064 Re: Prepare release announcement (Puppet Platform 5.5.17) The next point release in the Puppet 5.5 series, Puppet 5.5.17 is now available! The release contains bug fixes and minor improvements, including: The exec type’s onlyif and unless checks now return redacted output if it is marked sensitive You can now specify no_proxy as a Puppet setting, consistent with other http_proxy_* Puppet settings. Installation time on larger modules has been improved. Puppet can now set Windows service startup type to Auto-Start (Delayed). This version upgrades the Ruby version to 2.5.7 This version upgrades OpenSSL to 1.0.2t This version includes a security update to curl 7.66.0 For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/5.5/release_notes.html cc/Jean Bond to review, once Jean is good, @molly we should be good to send it. 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
Jira (PUP-10085) Prepare release announcement (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha assigned an issue to Nirupama Mantha Puppet / PUP-10085 Prepare release announcement (Puppet Platform 6.10.1) Change By: Nirupama Mantha Assignee: Bill Tang Nirupama Mantha 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.328054.1570145509000.1466.1571168160218%40Atlassian.JIRA.
Jira (PUP-10074) Prepare release announcement (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha assigned an issue to Nirupama Mantha Puppet / PUP-10074 Prepare release announcement (Puppet Platform 6.4.4) Change By: Nirupama Mantha Assignee: Bill Tang Nirupama Mantha 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.327758.1570050677000.1462.1571168040213%40Atlassian.JIRA.
Jira (PUP-10064) Prepare release announcement (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha assigned an issue to Nirupama Mantha Puppet / PUP-10064 Prepare release announcement (Puppet Platform 5.5.17) Change By: Nirupama Mantha Assignee: Bill Tang Nirupama Mantha 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.327718.1570050334000.1434.1571167080101%40Atlassian.JIRA.
Jira (PDB-4545) Update winston (PuppetDB 6.7.1)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4545 Update winston (PuppetDB 6.7.1) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/03 4:35 PM Due Date: 2019/10/16 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-4543) Bump versions, push directly, and tag (PuppetDB 6.7.1)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4543 Bump versions, push directly, and tag (PuppetDB 6.7.1) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/03 4:34 PM Due Date: 2019/10/11 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) (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 and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Disable automatic promotions: If this release will be released in a PE release, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. 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
Jira (PDB-4541) Merge-up, branch, and create pipelines (PuppetDB 6.7.1)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4541 Merge-up, branch, and create pipelines (PuppetDB 6.7.1) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/03 4:34 PM Due Date: 2019/10/08 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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/ 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: Merge 5.2.x -> 6.3.x Merge
Jira (PDB-4544) Check builds, promote to PE (PuppetDB 6.7.1)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4544 Check builds, promote to PE (PuppetDB 6.7.1) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/03 4:35 PM Due Date: 2019/10/11 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-4542) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.7.1)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4542 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.7.1) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/03 4:34 PM Due Date: 2019/10/08 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PUP-10086) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10086 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.10.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/03 4:32 PM Due Date: 2019/10/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10090) Communicate scope and timeline of next release (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10090 Communicate scope and timeline of next release (Puppet Platform 6.10.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/03 4:32 PM Due Date: 2019/10/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10089) Update Confluence and JIRA based on release (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10089 Update Confluence and JIRA based on release (Puppet Platform 6.10.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/03 4:32 PM Due Date: 2019/10/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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
Jira (PUP-10087) Publish documentation and updates and release notes (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10087 Publish documentation and updates and release notes (Puppet Platform 6.10.1) Issue Type: Task Assignee: Jean Bond Created: 2019/10/03 4:32 PM Due Date: 2019/10/15 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10088) Send release announcement (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10088 Send release announcement (Puppet Platform 6.10.1) Issue Type: Task Assignee: Molly Waggett Created: 2019/10/03 4:32 PM Due Date: 2019/10/15 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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.10.1 is now available".
Jira (PUP-10085) Prepare release announcement (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10085 Prepare release announcement (Puppet Platform 6.10.1) Issue Type: Task Assignee: Bill Tang Created: 2019/10/03 4:31 PM Due Date: 2019/10/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10082) Prepare JIRA and Confluence for release (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10082 Prepare JIRA and Confluence for release (Puppet Platform 6.10.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/03 4:31 PM Due Date: 2019/10/09 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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.10.1 and puppet-agent 6.10.1 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform
Jira (PUP-10081) Puppet Platform 6.10.1 Release - 2019-10-15
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10081 Puppet Platform 6.10.1 Release - 2019-10-15 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/10/03 4:31 PM Due Date: 2019/10/15 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.10.1 Release - 2019-10-15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10083) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10083 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.10.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/03 4:31 PM Due Date: 2019/10/09 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10084) Prepare documentation updates and release notes (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10084 Prepare documentation updates and release notes (Puppet Platform 6.10.1) Issue Type: Task Assignee: Jean Bond Created: 2019/10/03 4:31 PM Due Date: 2019/10/11 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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 (PDB-4539) Update winston (PuppetDB 6.3.5)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4539 Update winston (PuppetDB 6.3.5) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:15 PM Due Date: 2019/10/16 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-4537) Bump versions, push directly, and tag (PuppetDB 6.3.5)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4537 Bump versions, push directly, and tag (PuppetDB 6.3.5) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:14 PM Due Date: 2019/10/09 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) (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 and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Disable automatic promotions: If this release will be released in a PE release, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. 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
Jira (PDB-4535) Merge-up, branch, and create pipelines (PuppetDB 6.3.5)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4535 Merge-up, branch, and create pipelines (PuppetDB 6.3.5) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:14 PM Due Date: 2019/10/06 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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/ 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: Merge 5.2.x -> 6.3.x Merge
Jira (PDB-4538) Check builds, promote to PE (PuppetDB 6.3.5)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4538 Check builds, promote to PE (PuppetDB 6.3.5) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:14 PM Due Date: 2019/10/09 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-4536) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.5)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4536 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.5) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:14 PM Due Date: 2019/10/06 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PUP-10078) Update Confluence and JIRA based on release (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10078 Update Confluence and JIRA based on release (Puppet Platform 6.4.4) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:12 PM Due Date: 2019/10/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the
Jira (PUP-10079) Communicate scope and timeline of next release (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10079 Communicate scope and timeline of next release (Puppet Platform 6.4.4) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:12 PM Due Date: 2019/10/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10077) Send release announcement (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10077 Send release announcement (Puppet Platform 6.4.4) Issue Type: Task Assignee: Molly Waggett Created: 2019/10/02 2:12 PM Due Date: 2019/10/15 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.4.4 is now available".
Jira (PUP-10074) Prepare release announcement (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10074 Prepare release announcement (Puppet Platform 6.4.4) Issue Type: Task Assignee: Bill Tang Created: 2019/10/02 2:11 PM Due Date: 2019/10/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10073) Prepare documentation updates and release notes (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10073 Prepare documentation updates and release notes (Puppet Platform 6.4.4) Issue Type: Task Assignee: Jean Bond Created: 2019/10/02 2:11 PM Due Date: 2019/10/09 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10076) Publish documentation and updates and release notes (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10076 Publish documentation and updates and release notes (Puppet Platform 6.4.4) Issue Type: Task Assignee: Jean Bond Created: 2019/10/02 2:11 PM Due Date: 2019/10/15 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10075) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10075 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.4) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:11 PM Due Date: 2019/10/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10072) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10072 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.4) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:11 PM Due Date: 2019/10/07 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10071) Prepare JIRA and Confluence for release (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10071 Prepare JIRA and Confluence for release (Puppet Platform 6.4.4) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:10 PM Due Date: 2019/10/07 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.4.4 and puppet-agent 6.4.4 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PUP-10070) Puppet Platform 6.4.4 Release - 2019-10-15
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10070 Puppet Platform 6.4.4 Release - 2019-10-15 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/10/02 2:10 PM Due Date: 2019/10/15 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.4.4 Release - 2019-10-15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4534) Update winston (PuppetDB 5.2.10)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4534 Update winston (PuppetDB 5.2.10) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:09 PM Due Date: 2019/10/16 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-4530) Merge-up, branch, and create pipelines (PuppetDB 5.2.10)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4530 Merge-up, branch, and create pipelines (PuppetDB 5.2.10) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:08 PM Due Date: 2019/10/01 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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/ 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: Merge 5.2.x -> 6.3.x Merge
Jira (PDB-4532) Bump versions, push directly, and tag (PuppetDB 5.2.10)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4532 Bump versions, push directly, and tag (PuppetDB 5.2.10) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:08 PM Due Date: 2019/10/04 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) (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 and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Disable automatic promotions: If this release will be released in a PE release, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. 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
Jira (PDB-4533) Check builds, promote to PE (PuppetDB 5.2.10)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4533 Check builds, promote to PE (PuppetDB 5.2.10) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:08 PM Due Date: 2019/10/04 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-4531) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.10)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4531 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.10) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:08 PM Due Date: 2019/10/01 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PUP-10069) Communicate scope and timeline of next release (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10069 Communicate scope and timeline of next release (Puppet Platform 5.5.17) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:06 PM Due Date: 2019/10/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10068) Update Confluence and JIRA based on release (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10068 Update Confluence and JIRA based on release (Puppet Platform 5.5.17) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:06 PM Due Date: 2019/10/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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
Jira (PUP-10067) Send release announcement (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10067 Send release announcement (Puppet Platform 5.5.17) Issue Type: Task Assignee: Molly Waggett Created: 2019/10/02 2:06 PM Due Date: 2019/10/15 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 5.5.17 is now available".
Jira (PUP-10063) Prepare documentation updates and release notes (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10063 Prepare documentation updates and release notes (Puppet Platform 5.5.17) Issue Type: Task Assignee: Jean Bond Created: 2019/10/02 2:05 PM Due Date: 2019/10/04 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10060) Puppet Platform 5.5.17 Release - 2019-10-15
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10060 Puppet Platform 5.5.17 Release - 2019-10-15 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/10/02 2:05 PM Due Date: 2019/10/15 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 5.5.17 Release - 2019-10-15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10062) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10062 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.17) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:05 PM Due Date: 2019/10/02 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10065) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10065 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.17) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:05 PM Due Date: 2019/10/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10061) Prepare JIRA and Confluence for release (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10061 Prepare JIRA and Confluence for release (Puppet Platform 5.5.17) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:05 PM Due Date: 2019/10/02 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 5.5.17 and puppet-agent 5.5.17 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform
Jira (PUP-10066) Publish documentation and updates and release notes (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10066 Publish documentation and updates and release notes (Puppet Platform 5.5.17) Issue Type: Task Assignee: Jean Bond Created: 2019/10/02 2:05 PM Due Date: 2019/10/15 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10064) Prepare release announcement (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10064 Prepare release announcement (Puppet Platform 5.5.17) Issue Type: Task Assignee: Bill Tang Created: 2019/10/02 2:05 PM Due Date: 2019/10/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10046) Prepare release announcement (Puppet Platform 6.10.0)
Title: Message Title Nirupama Mantha commented on PUP-10046 Re: Prepare release announcement (Puppet Platform 6.10.0) The next release in the Platform 6 series, Platform 6.10.0 is now available! The release contains bug fixes and minor improvements, including: Query parameters for HTTP and HTTPS file resources are now preserved YAML output with special characters is now valid You can see the full list of changes in the release notes https://puppet.com/docs/puppet/latest/release_notes_puppet.html cc/ Jean Bond Bill Tang please review the release notes above. Eric Griswold you can use this once we get a thumbs up from Jean and Bill for the 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.326631.1569437002000.123730.1569963600338%40Atlassian.JIRA.
Jira (PDB-4468) Partitioning of resource_events: Migration test for initial creation of partitions
Title: Message Title Nirupama Mantha commented on PDB-4468 Re: Partitioning of resource_events: Migration test for initial creation of partitions Robert RolandCan you update the release notes field for this ticket? 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.319330.1564695363000.117354.1569541080247%40Atlassian.JIRA.
Jira (PDB-4466) Partitioning of resource_events: GC by dropping expired partitions
Title: Message Title Nirupama Mantha commented on PDB-4466 Re: Partitioning of resource_events: GC by dropping expired partitions Robert RolandCan you update the release notes field for this ticket? 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.319328.1564695244000.117346.1569541020257%40Atlassian.JIRA.
Jira (PDB-4467) Partitioning of resource_events: Migrate existing events to partitioned tables
Title: Message Title Nirupama Mantha commented on PDB-4467 Re: Partitioning of resource_events: Migrate existing events to partitioned tables Robert RolandCan you update the release notes field for this ticket? 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.319329.1564695312000.117350.1569541020273%40Atlassian.JIRA.
Jira (PDB-3284) PQL operators sometimes whitespace sensitive
Title: Message Title Nirupama Mantha commented on PDB-3284 Re: PQL operators sometimes whitespace sensitive Austin Blatt Can you update the release notes field for this ticket? 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.172549.148556000.117342.1569540960220%40Atlassian.JIRA.
Jira (PDB-4480) Create the catalog-inputs query endpoint
Title: Message Title Nirupama Mantha commented on PDB-4480 Re: Create the catalog-inputs query endpoint Can you update the release notes field for this ticket? 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.320756.1565732125000.117335.1569540780268%40Atlassian.JIRA.
Jira (PDB-4515) Merge-up, branch, and create pipelines (PuppetDB 6.7.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4515 Merge-up, branch, and create pipelines (PuppetDB 6.7.0) Issue Type: Task Assignee: Austin Blatt Created: 2019/09/25 11:47 AM Due Date: 2019/09/25 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) 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-4519) Update winston (PuppetDB 6.7.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4519 Update winston (PuppetDB 6.7.0) Issue Type: Task Assignee: Austin Blatt Created: 2019/09/25 11:48 AM Due Date: 2019/10/02 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) 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-4516) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.7.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4516 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.7.0) Issue Type: Task Assignee: Austin Blatt Created: 2019/09/25 11:47 AM Due Date: 2019/09/25 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) 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-4518) Check builds, promote to PE (PuppetDB 6.7.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4518 Check builds, promote to PE (PuppetDB 6.7.0) Issue Type: Task Assignee: Austin Blatt Created: 2019/09/25 11:47 AM Due Date: 2019/09/28 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) 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-4517) Bump versions, push directly, and tag (PuppetDB 6.7.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4517 Bump versions, push directly, and tag (PuppetDB 6.7.0) Issue Type: Task Assignee: Austin Blatt Created: 2019/09/25 11:47 AM Due Date: 2019/09/28 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) (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 (PUP-10049) Send release announcement (Puppet Platform 6.10.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10049 Send release announcement (Puppet Platform 6.10.0) Issue Type: Task Assignee: Eric Griswold Created: 2019/09/25 11:44 AM Due Date: 2019/10/01 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) 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.10.0 is now available".
Jira (PUP-10050) Update Confluence and JIRA based on release (Puppet Platform 6.10.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10050 Update Confluence and JIRA based on release (Puppet Platform 6.10.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/09/25 11:44 AM Due Date: 2019/10/02 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) 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
Jira (PUP-10051) Communicate scope and timeline of next release (Puppet Platform 6.10.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10051 Communicate scope and timeline of next release (Puppet Platform 6.10.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/09/25 11:44 AM Due Date: 2019/10/02 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) 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-10045) Prepare documentation updates and release notes (Puppet Platform 6.10.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10045 Prepare documentation updates and release notes (Puppet Platform 6.10.0) Issue Type: Task Assignee: Jean Bond Created: 2019/09/25 11:43 AM Due Date: 2019/09/28 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) 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-10046) Prepare release announcement (Puppet Platform 6.10.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10046 Prepare release announcement (Puppet Platform 6.10.0) Issue Type: Task Assignee: Bill Tang Created: 2019/09/25 11:43 AM Due Date: 2019/09/30 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) 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-10047) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.10.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10047 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.10.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/09/25 11:43 AM Due Date: 2019/09/30 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) 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-10048) Publish documentation and updates and release notes (Puppet Platform 6.10.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10048 Publish documentation and updates and release notes (Puppet Platform 6.10.0) Issue Type: Task Assignee: Jean Bond Created: 2019/09/25 11:43 AM Due Date: 2019/10/01 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) 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-10044) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.10.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10044 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.10.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/09/25 11:43 AM Due Date: 2019/09/26 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) 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-10043) Prepare JIRA and Confluence for release (Puppet Platform 6.10.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10043 Prepare JIRA and Confluence for release (Puppet Platform 6.10.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/09/25 11:42 AM Due Date: 2019/09/26 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-01) 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.10.0 and puppet-agent 6.10.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform
Jira (PUP-10042) Puppet Platform 6.10.0 Release - 2019-10-01
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10042 Puppet Platform 6.10.0 Release - 2019-10-01 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/09/25 11:42 AM Due Date: 2019/10/01 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.10.0 Release - 2019-10-01 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10005) Prepare release announcement (Puppet Platform 6.9.0)
Title: Message Title Nirupama Mantha commented on PUP-10005 Re: Prepare release announcement (Puppet Platform 6.9.0) Jean Bond Bill Tang please take a look and let me know if this looks good CC/ Morgan Rhodes you can send this once we get a thumbs up from Jean and Bill 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.323752.1567727666000.102460.1568751960306%40Atlassian.JIRA.
Jira (PUP-10005) Prepare release announcement (Puppet Platform 6.9.0)
Title: Message Title Nirupama Mantha commented on PUP-10005 Re: Prepare release announcement (Puppet Platform 6.9.0) The next release in the Platform 6 series, Platform 6.9.0 is now available! The release contains bug fixes and minor improvements, including: Agent startup logged at debug level in daemon mode serverip6 fact added Now the plugin command is included in puppet help output puppet module uninstall now works in FIPS mode You can see the full list of changes in the release notes https://puppet.com/docs/puppet/latest/release_notes_puppet.html 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.323752.1567727666000.102453.1568751900389%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Nirupama Mantha commented on PUP-10016 Re: Systemd provider is not correctly selected as the service provider if puppet is run as non root Please update release notes for this ticket accordingly 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.324178.1568121391000.92679.1568151180179%40Atlassian.JIRA.
Jira (PDB-4495) Merge-up, branch, and create pipelines (PuppetDB 6.6.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4495 Merge-up, branch, and create pipelines (PuppetDB 6.6.0) Issue Type: Task Assignee: Zachary Kent Created: 2019/09/05 4:57 PM Due Date: 2019/09/10 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) 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-4499) Update winston (PuppetDB 6.6.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4499 Update winston (PuppetDB 6.6.0) Issue Type: Task Assignee: Zachary Kent Created: 2019/09/05 4:58 PM Due Date: 2019/09/18 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) 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-4496) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.6.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4496 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.6.0) Issue Type: Task Assignee: Zachary Kent Created: 2019/09/05 4:57 PM Due Date: 2019/09/10 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) 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-4497) Bump versions, push directly, and tag (PuppetDB 6.6.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4497 Bump versions, push directly, and tag (PuppetDB 6.6.0) Issue Type: Task Assignee: Zachary Kent Created: 2019/09/05 4:57 PM Due Date: 2019/09/13 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) (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-4498) Check builds, promote to PE (PuppetDB 6.6.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4498 Check builds, promote to PE (PuppetDB 6.6.0) Issue Type: Task Assignee: Zachary Kent Created: 2019/09/05 4:57 PM Due Date: 2019/09/13 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) 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 (PUP-10008) Send release announcement (Puppet Platform 6.9.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10008 Send release announcement (Puppet Platform 6.9.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/09/05 4:55 PM Due Date: 2019/09/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) 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.9.0 is now available".
Jira (PUP-10009) Update Confluence and JIRA based on release (Puppet Platform 6.9.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10009 Update Confluence and JIRA based on release (Puppet Platform 6.9.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/09/05 4:55 PM Due Date: 2019/09/18 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the
Jira (PUP-10010) Communicate scope and timeline of next release (Puppet Platform 6.9.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10010 Communicate scope and timeline of next release (Puppet Platform 6.9.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/09/05 4:55 PM Due Date: 2019/09/18 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) 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-10001) Puppet Platform 6.9.0 Release - 2019-09-17
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10001 Puppet Platform 6.9.0 Release - 2019-09-17 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/09/05 4:54 PM Due Date: 2019/09/17 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.9.0 Release - 2019-09-17 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10002) Prepare JIRA and Confluence for release (Puppet Platform 6.9.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10002 Prepare JIRA and Confluence for release (Puppet Platform 6.9.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/09/05 4:54 PM Due Date: 2019/09/11 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) 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.9.0 and puppet-agent 6.9.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PUP-10007) Publish documentation and updates and release notes (Puppet Platform 6.9.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10007 Publish documentation and updates and release notes (Puppet Platform 6.9.0) Issue Type: Task Assignee: Jean Bond Created: 2019/09/05 4:54 PM Due Date: 2019/09/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) 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-10005) Prepare release announcement (Puppet Platform 6.9.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10005 Prepare release announcement (Puppet Platform 6.9.0) Issue Type: Task Assignee: Bill Tang Created: 2019/09/05 4:54 PM Due Date: 2019/09/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) 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-10004) Prepare documentation updates and release notes (Puppet Platform 6.9.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10004 Prepare documentation updates and release notes (Puppet Platform 6.9.0) Issue Type: Task Assignee: Jean Bond Created: 2019/09/05 4:54 PM Due Date: 2019/09/13 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) 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-10003) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.9.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10003 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.9.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/09/05 4:54 PM Due Date: 2019/09/11 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) 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-10006) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.9.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10006 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.9.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/09/05 4:54 PM Due Date: 2019/09/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-09-17) 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-9987) Update Confluence and JIRA based on release (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9987 Update Confluence and JIRA based on release (Puppet Platform 6.8.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/27 5:00 PM Due Date: 2019/08/29 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the
Jira (PUP-9988) Communicate scope and timeline of next release (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9988 Communicate scope and timeline of next release (Puppet Platform 6.8.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/27 5:00 PM Due Date: 2019/08/29 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 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-9986) Send release announcement (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9986 Send release announcement (Puppet Platform 6.8.1) Issue Type: Task Assignee: Sara Meisburger Created: 2019/08/27 5:00 PM Due Date: 2019/08/28 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 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.1 is now available".
Jira (PUP-9981) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9981 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.8.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/27 4:59 PM Due Date: 2019/08/27 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 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-9984) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9984 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.8.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/27 4:59 PM Due Date: 2019/08/27 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 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-9983) Prepare release announcement (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9983 Prepare release announcement (Puppet Platform 6.8.1) Issue Type: Task Assignee: Bill Tang Created: 2019/08/27 4:59 PM Due Date: 2019/08/27 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 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-9985) Publish documentation and updates and release notes (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9985 Publish documentation and 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/28 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 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-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
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
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)