Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title Sebastian Miclea commented on FACT-2847 Re: Facter 4 breaks rspec on fact test Hi Martin Alfke, It looks to me that there is something else in your test framework that makes makes some extra calls to Facter::Core::Execution. I could not manage to reproduce the second error on my machine, but managed to have the test passing with a generic stub to Facter::Core::Execution. Try adding allow(Facter::Core::Execution).to receive(:execute) to your before block. If you have multiple tests failing, I would suggest adding it to spec_helper so it won't create any syscalls while running tests. Let me know if this works out for you. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376201.1603820546000.67965.1604054820027%40Atlassian.JIRA.
Jira (PUP-10731) Setting facterng twice raises an exception
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10731 Setting facterng twice raises an exception Change By: Mihai Buzgau Sub-team: ghost Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376536.1604009521000.68021.1604064360096%40Atlassian.JIRA.
Jira (PUP-10731) Setting facterng twice raises an exception
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10731 Setting facterng twice raises an exception Change By: Mihai Buzgau Sprint: ghost-4.11 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376536.1604009521000.68020.1604064360047%40Atlassian.JIRA.
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title Martin Alfke commented on FACT-2847 Re: Facter 4 breaks rspec on fact test The whole code base is in a public github repo: https://github.com/tuxmea/workshop-demo-module/tree/ruby_workshop There are several facts which use Facter::Core::Execution.execute. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376201.1603820546000.68037.1604067060026%40Atlassian.JIRA.
Jira (PUP-10732) Puppet service report next prjected runtime
Title: Message Title Pat Riehecky created an issue Puppet / PUP-10732 Puppet service report next prjected runtime Issue Type: Improvement Assignee: Unassigned Created: 2020/10/30 7:36 AM Priority: Trivial Reporter: Pat Riehecky It would be helpful if the puppet service logged the next projected runtime. For example, I've got a run interval of 1 hour and a splay of 20 minutes. It would be nice if I could view the logs to get an estimate of when puppet is likely to run again on this host. I'd love to have this information logged when the service starts and after each run (so that I can see when the next one is likely). Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f93
Jira (PUP-3542) Write statefile in JSON
Title: Message Title Florin Dragos commented on PUP-3542 Re: Write statefile in JSON There are some issues with moving the state file from yaml to json format, the biggest one, being the value types. Json does not preserve the types, so if we write a symbol, it will read a string. This is one of the benefits when using yaml. The state file, as well as the transaction file contains strings and symbols for keys, as well for values. With json we can't have this, so it would mean changing a lot of code inside puppet to make it work. Another option that will read the correct type is marshal, but this has some security concerns, since it can load any arbitrary objects from from file. At this moment, the only viable option if we want to use json, is to write our own json serialiser (eg. like Microsoft did for the azure sdk - https://github.com/Azure/azure-sdk-for-ruby/blob/master/runtime/ms_rest/lib/ms_rest/serialization.rb ) and save the types, so we can read them back later. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.56207.141419759.68065.1604069820186%40Atlassian.JIRA.
Jira (PUP-10731) Setting facterng twice raises an exception
Title: Message Title Josh Cooper commented on PUP-10731 Re: Setting facterng twice raises an exception This was merged to master in bfd22200fc Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376536.1604009521000.68187.1604077560122%40Atlassian.JIRA.
Jira (PUP-10731) Setting facterng twice raises an exception
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10731 Setting facterng twice raises an exception Change By: Josh Cooper CI Pipeline/s: platform puppet-agent suite Release Notes: Bug Fix Release Notes Summary: Calling "puppet config set facterng true" twice would result in a failure. Now facterng is only enabled if it isn't already. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376536.1604009521000.68189.1604077620037%40Atlassian.JIRA.
Jira (PUP-7843) The list of reserved type names known to the parser validator is incomplete
Title: Message Title Josh Cooper commented on PUP-7843 Re: The list of reserved type names known to the parser validator is incomplete This passed puppet CI in 89d9333618. PEZ failures are unrelated, so resolving Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.205816.1502784101000.68327.1604081820180%40Atlassian.JIRA.
Jira (PDB-4877) Prefer JSON fact terminus for fact cache to YAML
Title: Message Title Josh Cooper commented on PDB-4877 Re: Prefer JSON fact terminus for fact cache to YAML One gotcha to watch out for is that symbols are not preserved when round-tripped through JSON. I assume that will not bite us with facts (since the agent sends them as JSON by default on the wire), but it did bite us on the agent when storing resource parameter names in its transactionstore cache, such as :ensure. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.371010.1599070036000.68416.1604086380169%40Atlassian.JIRA.
Jira (PUP-10735) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10735 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10733 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376618.160409203.68504.1604092080587%40Atlassian.JIRA.
Jira (PUP-10739) Publish documentation and updates and release notes (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10739 Publish documentation and updates and release notes (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10733 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376623.1604092048000.68512.1604092080834%40Atlassian.JIRA.
Jira (PUP-10739) Publish documentation and updates and release notes (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10739 Publish documentation and updates and release notes (Puppet Platform 6.20.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/10/30 2:07 PM Due Date: 2021/01/19 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10736) Prepare documentation updates and release notes (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10736 Prepare documentation updates and release notes (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10733 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376619.1604092033000.68506.1604092080606%40Atlassian.JIRA.
Jira (PUP-10736) Prepare documentation updates and release notes (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10736 Prepare documentation updates and release notes (Puppet Platform 6.20.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/10/30 2:07 PM Due Date: 2021/01/15 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10733) Puppet Platform 6.20.0 Release - 2021-01-19
Title: Message Title Eric Griswold created an issue Puppet / PUP-10733 Puppet Platform 6.20.0 Release - 2021-01-19 Issue Type: Epic Assignee: Nirupama Mantha Created: 2020/10/30 2:07 PM Due Date: 2021/01/19 Priority: Normal Reporter: Eric Griswold Puppet Platform 6.20.0 Release - 2021-01-19 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10741) Update Confluence and JIRA based on release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10741 Update Confluence and JIRA based on release (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:07 PM Due Date: 2021/01/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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 des
Jira (PUP-10734) Prepare JIRA and Confluence for release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10734 Prepare JIRA and Confluence for release (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:07 PM Due Date: 2021/01/13 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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.20.0 and puppet-agent 6.20.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-10738) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10738 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10733 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376622.1604092045000.68510.1604092080783%40Atlassian.JIRA.
Jira (PUP-10742) Communicate scope and timeline of next release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10742 Communicate scope and timeline of next release (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10733 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376627.1604092061000.68518.1604092081023%40Atlassian.JIRA.
Jira (PUP-10735) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10735 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:07 PM Due Date: 2021/01/13 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10737) Prepare release announcement (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10737 Prepare release announcement (Puppet Platform 6.20.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/10/30 2:07 PM Due Date: 2021/01/18 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Claire Cadman 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-10741) Update Confluence and JIRA based on release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10741 Update Confluence and JIRA based on release (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10733 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376626.1604092058000.68516.1604092080975%40Atlassian.JIRA.
Jira (PUP-10740) Send release announcement (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10740 Send release announcement (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10733 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376625.1604092055000.68514.1604092080887%40Atlassian.JIRA.
Jira (PUP-10738) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10738 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:07 PM Due Date: 2021/01/18 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10737) Prepare release announcement (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10737 Prepare release announcement (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10733 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376620.1604092039000.68508.1604092080695%40Atlassian.JIRA.
Jira (PUP-10740) Send release announcement (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10740 Send release announcement (Puppet Platform 6.20.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2020/10/30 2:07 PM Due Date: 2021/01/19 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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.20.0 is now available".
Jira (PUP-10742) Communicate scope and timeline of next release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10742 Communicate scope and timeline of next release (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:07 PM Due Date: 2021/01/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10734) Prepare JIRA and Confluence for release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10734 Prepare JIRA and Confluence for release (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10733 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376617.1604092027000.68502.1604092080499%40Atlassian.JIRA.
Jira (PUP-10745) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10745 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376640.1604092315000.68550.1604092320271%40Atlassian.JIRA.
Jira (PUP-10743) Puppet Platform 7.0.0 Release - 2020-11-17
Title: Message Title Eric Griswold created an issue Puppet / PUP-10743 Puppet Platform 7.0.0 Release - 2020-11-17 Issue Type: Epic Assignee: Nirupama Mantha Created: 2020/10/30 2:11 PM Due Date: 2020/11/17 Priority: Normal Reporter: Eric Griswold Puppet Platform 7.0.0 Release - 2020-11-17 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10745) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10745 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.0.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:11 PM Due Date: 2020/11/04 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-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-10744) Prepare JIRA and Confluence for release (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10744 Prepare JIRA and Confluence for release (Puppet Platform 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376639.1604092312000.68548.1604092320184%40Atlassian.JIRA.
Jira (PUP-10746) Prepare documentation updates and release notes (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10746 Prepare documentation updates and release notes (Puppet Platform 7.0.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/10/30 2:11 PM Due Date: 2020/11/06 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-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-10744) Prepare JIRA and Confluence for release (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10744 Prepare JIRA and Confluence for release (Puppet Platform 7.0.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:11 PM Due Date: 2020/11/04 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-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 7.0.0 and puppet-agent 7.0.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to re
Jira (PUP-10751) Update Confluence and JIRA based on release (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10751 Update Confluence and JIRA based on release (Puppet Platform 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376648.1604092341000.68562.1604092380556%40Atlassian.JIRA.
Jira (PUP-10751) Update Confluence and JIRA based on release (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10751 Update Confluence and JIRA based on release (Puppet Platform 7.0.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:12 PM Due Date: 2020/11/18 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-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 desc
Jira (PUP-10749) Publish documentation and updates and release notes (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10749 Publish documentation and updates and release notes (Puppet Platform 7.0.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/10/30 2:12 PM Due Date: 2020/11/17 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-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-10747) Prepare release announcement (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10747 Prepare release announcement (Puppet Platform 7.0.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/10/30 2:12 PM Due Date: 2020/11/16 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-17) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Claire Cadman 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-10752) Communicate scope and timeline of next release (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10752 Communicate scope and timeline of next release (Puppet Platform 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376649.1604092344000.68564.1604092380643%40Atlassian.JIRA.
Jira (PUP-10749) Publish documentation and updates and release notes (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10749 Publish documentation and updates and release notes (Puppet Platform 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376645.160409233.68558.1604092380451%40Atlassian.JIRA.
Jira (PUP-10750) Send release announcement (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10750 Send release announcement (Puppet Platform 7.0.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2020/10/30 2:12 PM Due Date: 2020/11/17 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-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 7.0.0 is now available".
Jira (PUP-10747) Prepare release announcement (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10747 Prepare release announcement (Puppet Platform 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376642.1604092321000.68554.1604092380275%40Atlassian.JIRA.
Jira (PUP-10750) Send release announcement (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10750 Send release announcement (Puppet Platform 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376647.1604092337000.68560.1604092380545%40Atlassian.JIRA.
Jira (PUP-10748) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10748 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.0.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:12 PM Due Date: 2020/11/16 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-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-10748) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10748 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376644.1604092327000.68556.1604092380363%40Atlassian.JIRA.
Jira (PUP-10746) Prepare documentation updates and release notes (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10746 Prepare documentation updates and release notes (Puppet Platform 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376641.1604092318000.68552.1604092380186%40Atlassian.JIRA.
Jira (PUP-10752) Communicate scope and timeline of next release (Puppet Platform 7.0.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10752 Communicate scope and timeline of next release (Puppet Platform 7.0.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:12 PM Due Date: 2020/11/18 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-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 (PDB-4950) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.0.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-4950 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.0.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/10/30 2:13 PM Due Date: 2020/11/03 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-17) Ensure all tickets referenced in the commit log have a the release's fixVersion, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by checking out the branches you will be releasing, ensuring they are in sync with the upstream puppetlabs repo and running the rake task bundle install; bundle exec rake release:reconcile[NEXT_VER,LAST_VER] This assumes you have the puppetdb repo as the cwd and the pe repo at ../pe-puppetdb-extensions. These can be overridden by the PDB_PATH and PDB_PE_PATH environment variables. The rake task will explain any mismatches that exist between Jira and the repos and ask you to investigate any tickets that do not start with a PDB ticket, (maint), (docs), or (i18n) Add Comment
Jira (PDB-4952) Bump versions, push directly, and tag (PuppetDB 7.0.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4952 Bump versions, push directly, and tag (PuppetDB 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376669.160409240.68573.1604092440531%40Atlassian.JIRA.
Jira (PDB-4949) Merge-up, branch, and create pipelines (PuppetDB 7.0.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4949 Merge-up, branch, and create pipelines (PuppetDB 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.37.1604092391000.68567.1604092440268%40Atlassian.JIRA.
Jira (PDB-4953) Check builds, promote to PE (PuppetDB 7.0.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-4953 Check builds, promote to PE (PuppetDB 7.0.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/10/30 2:13 PM Due Date: 2020/11/06 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-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. If a release branch has already been cut Rebuild the pacakge promotion job with the release branch set instead of master or 2018.1.x. Once it's promoted to the release branch checkout the release branch of enterprise-dist locally and verify that all platforms have the same tagged version of pe-puppetdb bundle exec rake report:packages If there were any important dependency bumps, such as to fix a bug or CVE, verify that they were updated by navigating to the release and then to the pe-puppetdb package on [pebuildinfo|pebuildinfo.slice.puppetlabs.net/].
Jira (PDB-4949) Merge-up, branch, and create pipelines (PuppetDB 7.0.0)
Title: Message Title
Eric Griswold created an issue
PuppetDB / PDB-4949
Merge-up, branch, and create pipelines (PuppetDB 7.0.0)
Issue Type:
Task
Assignee:
Zachary Kent
Created:
2020/10/30 2:13 PM
Due Date:
2020/11/03
Priority:
Normal
Reporter:
Eric Griswold
(Initial planned release date: 2020-11-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
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 -> master
Important: Do this for both the core puppetdb repo and the pe-puppetdb-extensions repo! These should be submitted as PRs and merged after tests pass, if there's anything remotely interesting about the merges. If the merges are boring, then direct push is fine. Then, prepare the branch for release:
Jira (PDB-4954) Update winston (PuppetDB 7.0.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4954 Update winston (PuppetDB 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376672.160409241.68577.1604092440707%40Atlassian.JIRA.
Jira (PDB-4951) Draft release notes (PuppetDB 7.0.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-4951 Draft release notes (PuppetDB 7.0.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/10/30 2:13 PM Due Date: 2020/11/15 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-17) Write release notes for the release based on the tickets found in the previous step. Check any tickets for a docs tab with desired information. The release notes go in puppetdb\/documentation\/release_notes.markdown. Request review from the docs team by pinging @clairecadman in the opened PR, at least one day before Ready to Ship The opened PR should be approved prior to a go\/no-go. Release notes must be ready before a go. Docs are built daily and at release time. If notes need to be published out of band ask in `#prod-docs`.
Jira (PDB-4951) Draft release notes (PuppetDB 7.0.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4951 Draft release notes (PuppetDB 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376668.1604092398000.68571.1604092440443%40Atlassian.JIRA.
Jira (PDB-4952) Bump versions, push directly, and tag (PuppetDB 7.0.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-4952 Bump versions, push directly, and tag (PuppetDB 7.0.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/10/30 2:13 PM Due Date: 2020/11/06 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-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 and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Check that puppetdb and pe-puppetdb-extensions are on the same version of clj-parent, and that is the same clj-parent version that puppetserver will release with. Disable automatic promotions: If a PE release branch has not been cut, 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.
Jira (PDB-4954) Update winston (PuppetDB 7.0.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-4954 Update winston (PuppetDB 7.0.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/10/30 2:13 PM Due Date: 2020/11/18 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-11-17) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4950) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.0.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4950 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376667.1604092395000.68569.1604092440355%40Atlassian.JIRA.
Jira (PDB-4953) Check builds, promote to PE (PuppetDB 7.0.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4953 Check builds, promote to PE (PuppetDB 7.0.0) Change By: Eric Griswold Epic Link: PUP-10743 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376670.1604092404000.68575.1604092440620%40Atlassian.JIRA.
Jira (PUP-10754) Prepare JIRA and Confluence for release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10754 Prepare JIRA and Confluence for release (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10753 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376674.160409257.68651.1604092620311%40Atlassian.JIRA.
Jira (PUP-10761) Update Confluence and JIRA based on release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10761 Update Confluence and JIRA based on release (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:16 PM Due Date: 2021/01/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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 des
Jira (PUP-10753) Puppet Platform 6.20.0 Release - 2021-01-19
Title: Message Title Eric Griswold created an issue Puppet / PUP-10753 Puppet Platform 6.20.0 Release - 2021-01-19 Issue Type: Epic Assignee: Nirupama Mantha Created: 2020/10/30 2:16 PM Due Date: 2021/01/19 Priority: Normal Reporter: Eric Griswold Puppet Platform 6.20.0 Release - 2021-01-19 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10758) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10758 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10753 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376679.1604092586000.68659.1604092620667%40Atlassian.JIRA.
Jira (PUP-10759) Publish documentation and updates and release notes (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10759 Publish documentation and updates and release notes (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10753 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376680.1604092589000.68661.1604092620755%40Atlassian.JIRA.
Jira (PUP-10760) Send release announcement (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10760 Send release announcement (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10753 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376682.1604092596000.68663.1604092620847%40Atlassian.JIRA.
Jira (PUP-10759) Publish documentation and updates and release notes (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10759 Publish documentation and updates and release notes (Puppet Platform 6.20.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/10/30 2:16 PM Due Date: 2021/01/19 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10758) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10758 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:16 PM Due Date: 2021/01/18 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10757) Prepare release announcement (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10757 Prepare release announcement (Puppet Platform 6.20.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/10/30 2:16 PM Due Date: 2021/01/18 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Claire Cadman 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-10756) Prepare documentation updates and release notes (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10756 Prepare documentation updates and release notes (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10753 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376676.1604092576000.68655.1604092620491%40Atlassian.JIRA.
Jira (PUP-10755) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10755 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:16 PM Due Date: 2021/01/13 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10754) Prepare JIRA and Confluence for release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10754 Prepare JIRA and Confluence for release (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:16 PM Due Date: 2021/01/13 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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.20.0 and puppet-agent 6.20.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-10755) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10755 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10753 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376675.1604092573000.68653.1604092620403%40Atlassian.JIRA.
Jira (PUP-10756) Prepare documentation updates and release notes (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10756 Prepare documentation updates and release notes (Puppet Platform 6.20.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/10/30 2:16 PM Due Date: 2021/01/15 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10760) Send release announcement (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10760 Send release announcement (Puppet Platform 6.20.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2020/10/30 2:16 PM Due Date: 2021/01/19 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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.20.0 is now available".
Jira (PUP-10761) Update Confluence and JIRA based on release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10761 Update Confluence and JIRA based on release (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10753 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376683.1604092599000.68665.1604092620935%40Atlassian.JIRA.
Jira (PUP-10757) Prepare release announcement (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10757 Prepare release announcement (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10753 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376677.1604092579000.68657.1604092620580%40Atlassian.JIRA.
Jira (PUP-10764) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10764 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:33 PM Due Date: 2021/01/13 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10762) Puppet Platform 6.20.0 Release - 2021-01-19
Title: Message Title Eric Griswold created an issue Puppet / PUP-10762 Puppet Platform 6.20.0 Release - 2021-01-19 Issue Type: Epic Assignee: Nirupama Mantha Created: 2020/10/30 2:33 PM Due Date: 2021/01/19 Priority: Normal Reporter: Eric Griswold Puppet Platform 6.20.0 Release - 2021-01-19 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10765) Prepare documentation updates and release notes (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10765 Prepare documentation updates and release notes (Puppet Platform 6.20.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/10/30 2:33 PM Due Date: 2021/01/15 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10765) Prepare documentation updates and release notes (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10765 Prepare documentation updates and release notes (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10762 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376689.1604093626000.68701.1604093640476%40Atlassian.JIRA.
Jira (PUP-10766) Prepare release announcement (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10766 Prepare release announcement (Puppet Platform 6.20.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/10/30 2:33 PM Due Date: 2021/01/18 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Claire Cadman 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-10764) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10764 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10762 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376688.1604093623000.68699.1604093640388%40Atlassian.JIRA.
Jira (PUP-10767) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10767 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10762 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376692.1604093636000.68705.1604093640575%40Atlassian.JIRA.
Jira (PUP-10766) Prepare release announcement (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10766 Prepare release announcement (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10762 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376690.1604093629000.68703.1604093640527%40Atlassian.JIRA.
Jira (PUP-10767) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10767 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:33 PM Due Date: 2021/01/18 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10763) Prepare JIRA and Confluence for release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10763 Prepare JIRA and Confluence for release (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:33 PM Due Date: 2021/01/13 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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.20.0 and puppet-agent 6.20.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-10763) Prepare JIRA and Confluence for release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10763 Prepare JIRA and Confluence for release (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10762 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376687.160409362.68697.1604093640299%40Atlassian.JIRA.
Jira (PUP-10768) Publish documentation and updates and release notes (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10768 Publish documentation and updates and release notes (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10762 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376693.160409364.68708.1604093700224%40Atlassian.JIRA.
Jira (PUP-10770) Update Confluence and JIRA based on release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10770 Update Confluence and JIRA based on release (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10762 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376696.1604093651000.68712.1604093700399%40Atlassian.JIRA.
Jira (PUP-10770) Update Confluence and JIRA based on release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10770 Update Confluence and JIRA based on release (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:34 PM Due Date: 2021/01/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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 des
Jira (PUP-10769) Send release announcement (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10769 Send release announcement (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10762 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376695.1604093647000.68710.1604093700312%40Atlassian.JIRA.
Jira (PUP-10771) Communicate scope and timeline of next release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10771 Communicate scope and timeline of next release (Puppet Platform 6.20.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/10/30 2:34 PM Due Date: 2021/01/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10768) Publish documentation and updates and release notes (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10768 Publish documentation and updates and release notes (Puppet Platform 6.20.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/10/30 2:34 PM Due Date: 2021/01/19 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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-10769) Send release announcement (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10769 Send release announcement (Puppet Platform 6.20.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2020/10/30 2:34 PM Due Date: 2021/01/19 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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.20.0 is now available".
Jira (PUP-10771) Communicate scope and timeline of next release (Puppet Platform 6.20.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10771 Communicate scope and timeline of next release (Puppet Platform 6.20.0) Change By: Eric Griswold Epic Link: PUP-10762 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376697.1604093654000.68714.1604093700487%40Atlassian.JIRA.
Jira (PDB-4957) Draft release notes (PuppetDB 6.14.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-4957 Draft release notes (PuppetDB 6.14.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/10/30 2:35 PM Due Date: 2021/01/17 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) Write release notes for the release based on the tickets found in the previous step. Check any tickets for a docs tab with desired information. The release notes go in puppetdb\/documentation\/release_notes.markdown. Request review from the docs team by pinging @clairecadman in the opened PR, at least one day before Ready to Ship The opened PR should be approved prior to a go\/no-go. Release notes must be ready before a go. Docs are built daily and at release time. If notes need to be published out of band ask in `#prod-docs`.
Jira (PDB-4959) Check builds, promote to PE (PuppetDB 6.14.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4959 Check builds, promote to PE (PuppetDB 6.14.0) Change By: Eric Griswold Epic Link: PUP-10762 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376718.1604093717000.68730.1604093760744%40Atlassian.JIRA.
Jira (PDB-4955) Merge-up, branch, and create pipelines (PuppetDB 6.14.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4955 Merge-up, branch, and create pipelines (PuppetDB 6.14.0) Change By: Eric Griswold Epic Link: PUP-10762 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376714.1604093705000.68722.1604093760387%40Atlassian.JIRA.
Jira (PDB-4959) Check builds, promote to PE (PuppetDB 6.14.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-4959 Check builds, promote to PE (PuppetDB 6.14.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/10/30 2:35 PM Due Date: 2021/01/15 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-01-19) 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. If a release branch has already been cut Rebuild the pacakge promotion job with the release branch set instead of master or 2018.1.x. Once it's promoted to the release branch checkout the release branch of enterprise-dist locally and verify that all platforms have the same tagged version of pe-puppetdb bundle exec rake report:packages If there were any important dependency bumps, such as to fix a bug or CVE, verify that they were updated by navigating to the release and then to the pe-puppetdb package on [pebuildinfo|pebuildinfo.slice.puppetlabs.net/].
