Jira (PDB-5609) Remove SUSE Linux Enterprise Server 11 (x86-64) from puppetdb pipelines
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5609 Remove SUSE Linux Enterprise Server 11 (x86-64) from puppetdb pipelines Change By: Eric Griswold Team: Release Engineering Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.482690.1678401181000.3335.1687382460031%40Atlassian.JIRA.
Jira (PDB-5608) Remove SUSE Linux Enterprise Server 11 (i386) from puppetdb pipelines
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5608 Remove SUSE Linux Enterprise Server 11 (i386) from puppetdb pipelines Change By: Eric Griswold Team: Release Engineering Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.482659.167840107.3334.1687382400074%40Atlassian.JIRA.
Jira (PDB-5607) Remove Red Hat Enterprise Linux 7 (ppc64le) from puppetdb pipelines
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5607 Remove Red Hat Enterprise Linux 7 (ppc64le) from puppetdb pipelines Change By: Eric Griswold Team: Release Engineering Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.482628.167840071.3331.1687382280031%40Atlassian.JIRA.
Jira (PDB-5606) Remove Windows Server 2008R2 from puppetdb pipelines
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5606 Remove Windows Server 2008R2 from puppetdb pipelines Change By: Eric Griswold Team: Release Engineering Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.482597.1678400448000.3302.1687380240031%40Atlassian.JIRA.
Jira (PUP-11839) PDK Downloads Erroring
Title: Message Title Eric Griswold commented on PUP-11839 Re: PDK Downloads Erroring We saw multiple reports of this but we cannot reproduce it. Please report back if its still a problem please post the complete output. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.484440.1681740231000.8316.1682455500105%40Atlassian.JIRA.
Jira (PDB-5414) Check builds, promote to PE (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5414 Check builds, promote to PE (Puppet Platform 6.26.0) Issue Type: Task Assignee: Stel Abrego Created: 2022/01/05 2:57 PM Due Date: 2022/01/14 Priority: Normal Reporter: Eric Griswold Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet
Jira (PDB-5415) Update ticket templates (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5415 Update ticket templates (Puppet Platform 6.26.0) Issue Type: Task Assignee: Stel Abrego Created: 2022/01/05 2:57 PM Due Date: 2022/01/19 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) If appropriate, raise a PR to adjust the ticket templates more accurate for the next time. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PDB-5415) Update ticket templates (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5415 Update ticket templates (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428714.1641423434000.13938.1641423481261%40Atlassian.JIRA.
Jira (PDB-5412) Draft release notes (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5412 Draft release notes (Puppet Platform 6.26.0) Issue Type: Task Assignee: Stel Abrego Created: 2022/01/05 2:57 PM Due Date: 2022/01/16 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) Ensure all tickets have release notes. This query, once you've reconciled the Jira ticket fix versions in the previous step and configured the query with the current release version(s), will identify tickets whose release notes are not complete. Ask your team members to complete any tickets that need release notes (if the ticket's release note is simple you may write release notes for other people's tickets, but you certainly don't have to). Write release notes for the release based on the tickets found in the previous step. One of the simplest ways to gather release notes (once you've completed the step above to ensure every ticket that needs a release note has one) is to use this Jira query be sure to replace the fixVersions with the versions you are releasing and if you don't see release notes you'll need to verify that you're in List View and add the "Release Notes", "Release Notes Summary", and "fixVersion/s" columns to the page. All those view settings are configured in the top right via the two drop-downs below Share, Export, and Tools. Check any tickets for a docs tab with desired information. The release notes go in puppetdb\/documentation\/release_notes.markdown.
Jira (PDB-5412) Draft release notes (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5412 Draft release notes (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428711.164142342.13932.1641423480993%40Atlassian.JIRA.
Jira (PDB-5414) Check builds, promote to PE (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5414 Check builds, promote to PE (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428713.1641423429000.13936.1641423481173%40Atlassian.JIRA.
Jira (PDB-5413) Bump versions, push directly, and tag (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5413 Bump versions, push directly, and tag (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428712.1641423424000.13934.1641423481085%40Atlassian.JIRA.
Jira (PDB-5413) Bump versions, push directly, and tag (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5413 Bump versions, push directly, and tag (Puppet Platform 6.26.0) Issue Type: Task Assignee: Stel Abrego Created: 2022/01/05 2:57 PM Due Date: 2022/01/14 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release 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-5411) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5411 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428710.1641423414000.13915.1641423420200%40Atlassian.JIRA.
Jira (PDB-5411) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5411 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 6.26.0) Issue Type: Task Assignee: Stel Abrego Created: 2022/01/05 2:56 PM Due Date: 2022/01/11 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) Ensure all tickets referenced in the commit log have 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-5410) Merge-up, branch, and create pipelines (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5410 Merge-up, branch, and create pipelines (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428709.164142341.13913.1641423420185%40Atlassian.JIRA.
Jira (PDB-5410) Merge-up, branch, and create pipelines (Puppet Platform 6.26.0)
Title: Message Title
Eric Griswold created an issue
PuppetDB / PDB-5410
Merge-up, branch, and create pipelines (Puppet Platform 6.26.0)
Issue Type:
Task
Assignee:
Stel Abrego
Created:
2022/01/05 2:56 PM
Due Date:
2022/01/11
Priority:
Normal
Reporter:
Eric Griswold
(Initial planned release date: 2022-01-18) 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).
jenkins: main
jenkins: 6.x
travis: puppetdb
travis: pe-puppetdb-extensions
Do merge-ups:
Merge 6.x -> main
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:
SKIP ALL REMAINING STEPS - We are leaving them here until we have a better place to document the process to create a new branch. When we release a new Y version we do it off of main and cut a maintained branch later (if at all).
Jira (PUP-11426) Communicate scope and timeline of next release (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11426 Communicate scope and timeline of next release (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428695.1641423315000.13909.1641423360344%40Atlassian.JIRA.
Jira (PUP-11426) Communicate scope and timeline of next release (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11426 Communicate scope and timeline of next release (Puppet Platform 6.26.0) Issue Type: Task Assignee: Alex Rodriguez Created: 2022/01/05 2:55 PM Due Date: 2022/01/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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-11423) Publish documentation and updates and release notes (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11423 Publish documentation and updates and release notes (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428691.1641423299000.13903.1641423360167%40Atlassian.JIRA.
Jira (PUP-11425) Update Confluence and JIRA based on release (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11425 Update Confluence and JIRA based on release (Puppet Platform 6.26.0) Issue Type: Task Assignee: Alex Rodriguez Created: 2022/01/05 2:55 PM Due Date: 2022/01/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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-11425) Update Confluence and JIRA based on release (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11425 Update Confluence and JIRA based on release (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428694.1641423312000.13907.1641423360326%40Atlassian.JIRA.
Jira (PUP-11424) Send release announcement (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11424 Send release announcement (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428693.1641423307000.13905.1641423360273%40Atlassian.JIRA.
Jira (PUP-11424) Send release announcement (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11424 Send release announcement (Puppet Platform 6.26.0) Issue Type: Task Assignee: Isaac Hammes Created: 2022/01/05 2:55 PM Due Date: 2022/01/18 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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.26.0 is now available"
Jira (PUP-11422) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11422 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.26.0) Issue Type: Task Assignee: Alex Rodriguez Created: 2022/01/05 2:54 PM Due Date: 2022/01/17 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in #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-11419) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11419 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428686.1641423276000.13889.1641423300457%40Atlassian.JIRA.
Jira (PUP-11422) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11422 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428690.1641423293000.13897.1641423300761%40Atlassian.JIRA.
Jira (PUP-11421) Prepare release announcement (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11421 Prepare release announcement (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428688.1641423284000.13893.1641423300652%40Atlassian.JIRA.
Jira (PUP-11418) Prepare JIRA and Confluence for release (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11418 Prepare JIRA and Confluence for release (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428685.1641423272000.13887.1641423300361%40Atlassian.JIRA.
Jira (PUP-11421) Prepare release announcement (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11421 Prepare release announcement (Puppet Platform 6.26.0) Issue Type: Task Assignee: Parker Leach Created: 2022/01/05 2:54 PM Due Date: 2022/01/17 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping parker.leach 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-11419) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11419 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.26.0) Issue Type: Task Assignee: Alex Rodriguez Created: 2022/01/05 2:54 PM Due Date: 2022/01/12 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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-11418) Prepare JIRA and Confluence for release (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11418 Prepare JIRA and Confluence for release (Puppet Platform 6.26.0) Issue Type: Task Assignee: Alex Rodriguez Created: 2022/01/05 2:54 PM Due Date: 2022/01/12 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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.26.0 and puppet-agent 6.26.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-11417) Puppet Platform 6.26.0 Release - 2022-01-18
Title: Message Title Eric Griswold created an issue Puppet / PUP-11417 Puppet Platform 6.26.0 Release - 2022-01-18 Issue Type: Epic Assignee: Alex Rodriguez Created: 2022/01/05 2:54 PM Due Date: 2022/01/18 Priority: Normal Reporter: Eric Griswold Puppet Platform 6.26.0 Release - 2022-01-18 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-11420) Prepare documentation updates and release notes (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11420 Prepare documentation updates and release notes (Puppet Platform 6.26.0) Issue Type: Task Assignee: Parker Leach Created: 2022/01/05 2:54 PM Due Date: 2022/01/14 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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-11423) Publish documentation and updates and release notes (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11423 Publish documentation and updates and release notes (Puppet Platform 6.26.0) Issue Type: Task Assignee: Parker Leach Created: 2022/01/05 2:54 PM Due Date: 2022/01/18 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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-11420) Prepare documentation updates and release notes (Puppet Platform 6.26.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11420 Prepare documentation updates and release notes (Puppet Platform 6.26.0) Change By: Eric Griswold Epic Link: PUP-11417 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428687.164142328.13891.1641423300594%40Atlassian.JIRA.
Jira (PDB-5408) Check builds, promote to PE (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5408 Check builds, promote to PE (Puppet Platform 7.14.0) Issue Type: Task Assignee: Stel Abrego Created: 2022/01/05 2:20 PM Due Date: 2022/01/14 Priority: Normal Reporter: Eric Griswold Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet
Jira (PDB-5409) Update ticket templates (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5409 Update ticket templates (Puppet Platform 7.14.0) Issue Type: Task Assignee: Stel Abrego Created: 2022/01/05 2:20 PM Due Date: 2022/01/19 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) If appropriate, raise a PR to adjust the ticket templates more accurate for the next time. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PDB-5405) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5405 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428669.1641421201000.13803.1641421260807%40Atlassian.JIRA.
Jira (PDB-5405) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5405 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.14.0) Issue Type: Task Assignee: Stel Abrego Created: 2022/01/05 2:20 PM Due Date: 2022/01/11 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) Ensure all tickets referenced in the commit log have 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-5409) Update ticket templates (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5409 Update ticket templates (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428673.164142122.13811.1641421261133%40Atlassian.JIRA.
Jira (PDB-5408) Check builds, promote to PE (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5408 Check builds, promote to PE (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428672.1641421216000.13809.1641421261042%40Atlassian.JIRA.
Jira (PDB-5406) Draft release notes (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5406 Draft release notes (Puppet Platform 7.14.0) Issue Type: Task Assignee: Stel Abrego Created: 2022/01/05 2:20 PM Due Date: 2022/01/16 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) Ensure all tickets have release notes. This query, once you've reconciled the Jira ticket fix versions in the previous step and configured the query with the current release version(s), will identify tickets whose release notes are not complete. Ask your team members to complete any tickets that need release notes (if the ticket's release note is simple you may write release notes for other people's tickets, but you certainly don't have to). Write release notes for the release based on the tickets found in the previous step. One of the simplest ways to gather release notes (once you've completed the step above to ensure every ticket that needs a release note has one) is to use this Jira query be sure to replace the fixVersions with the versions you are releasing and if you don't see release notes you'll need to verify that you're in List View and add the "Release Notes", "Release Notes Summary", and "fixVersion/s" columns to the page. All those view settings are configured in the top right via the two drop-downs below Share, Export, and Tools. Check any tickets for a docs tab with desired information. The release notes go in puppetdb\/documentation\/release_notes.markdown.
Jira (PDB-5406) Draft release notes (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5406 Draft release notes (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428670.1641421205000.13805.1641421260861%40Atlassian.JIRA.
Jira (PDB-5404) Merge-up, branch, and create pipelines (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5404 Merge-up, branch, and create pipelines (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428668.1641421197000.13801.1641421260750%40Atlassian.JIRA.
Jira (PDB-5407) Bump versions, push directly, and tag (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5407 Bump versions, push directly, and tag (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428671.1641421209000.13807.1641421260948%40Atlassian.JIRA.
Jira (PDB-5407) Bump versions, push directly, and tag (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5407 Bump versions, push directly, and tag (Puppet Platform 7.14.0) Issue Type: Task Assignee: Stel Abrego Created: 2022/01/05 2:20 PM Due Date: 2022/01/14 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release 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-5404) Merge-up, branch, and create pipelines (Puppet Platform 7.14.0)
Title: Message Title
Eric Griswold created an issue
PuppetDB / PDB-5404
Merge-up, branch, and create pipelines (Puppet Platform 7.14.0)
Issue Type:
Task
Assignee:
Stel Abrego
Created:
2022/01/05 2:19 PM
Due Date:
2022/01/11
Priority:
Normal
Reporter:
Eric Griswold
(Initial planned release date: 2022-01-18) 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).
jenkins: main
jenkins: 6.x
travis: puppetdb
travis: pe-puppetdb-extensions
Do merge-ups:
Merge 6.x -> main
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:
SKIP ALL REMAINING STEPS - We are leaving them here until we have a better place to document the process to create a new branch. When we release a new Y version we do it off of main and cut a maintained branch later (if at all).
Jira (PUP-11412) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11412 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428649.1641421079000.13777.1641421140257%40Atlassian.JIRA.
Jira (PUP-11415) Update Confluence and JIRA based on release (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11415 Update Confluence and JIRA based on release (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428653.1641421099000.13783.1641421140497%40Atlassian.JIRA.
Jira (PUP-11415) Update Confluence and JIRA based on release (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11415 Update Confluence and JIRA based on release (Puppet Platform 7.14.0) Issue Type: Task Assignee: Alex Rodriguez Created: 2022/01/05 2:18 PM Due Date: 2022/01/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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-11413) Publish documentation and updates and release notes (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11413 Publish documentation and updates and release notes (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428650.1641421083000.13779.1641421140353%40Atlassian.JIRA.
Jira (PUP-11413) Publish documentation and updates and release notes (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11413 Publish documentation and updates and release notes (Puppet Platform 7.14.0) Issue Type: Task Assignee: Parker Leach Created: 2022/01/05 2:18 PM Due Date: 2022/01/18 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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-11416) Communicate scope and timeline of next release (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11416 Communicate scope and timeline of next release (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428654.1641421103000.13785.1641421140548%40Atlassian.JIRA.
Jira (PUP-11416) Communicate scope and timeline of next release (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11416 Communicate scope and timeline of next release (Puppet Platform 7.14.0) Issue Type: Task Assignee: Alex Rodriguez Created: 2022/01/05 2:18 PM Due Date: 2022/01/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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-11414) Send release announcement (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11414 Send release announcement (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428652.1641421095000.13781.1641421140403%40Atlassian.JIRA.
Jira (PUP-11414) Send release announcement (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11414 Send release announcement (Puppet Platform 7.14.0) Issue Type: Task Assignee: Isaac Hammes Created: 2022/01/05 2:18 PM Due Date: 2022/01/18 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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.14.0 is now available"
Jira (PUP-11408) Prepare JIRA and Confluence for release (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11408 Prepare JIRA and Confluence for release (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428644.1641421054000.13769.1641421080357%40Atlassian.JIRA.
Jira (PUP-11411) Prepare release announcement (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11411 Prepare release announcement (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428647.1641421071000.13775.1641421080416%40Atlassian.JIRA.
Jira (PUP-11410) Prepare documentation updates and release notes (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11410 Prepare documentation updates and release notes (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428646.1641421063000.13773.1641421080402%40Atlassian.JIRA.
Jira (PUP-11411) Prepare release announcement (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11411 Prepare release announcement (Puppet Platform 7.14.0) Issue Type: Task Assignee: Parker Leach Created: 2022/01/05 2:17 PM Due Date: 2022/01/17 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping parker.leach 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-11408) Prepare JIRA and Confluence for release (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11408 Prepare JIRA and Confluence for release (Puppet Platform 7.14.0) Issue Type: Task Assignee: Alex Rodriguez Created: 2022/01/05 2:17 PM Due Date: 2022/01/12 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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.14.0 and puppet-agent 7.14.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-11409) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11409 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.14.0) Issue Type: Task Assignee: Alex Rodriguez Created: 2022/01/05 2:17 PM Due Date: 2022/01/12 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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-11410) Prepare documentation updates and release notes (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11410 Prepare documentation updates and release notes (Puppet Platform 7.14.0) Issue Type: Task Assignee: Parker Leach Created: 2022/01/05 2:17 PM Due Date: 2022/01/14 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 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-11409) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11409 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.14.0) Change By: Eric Griswold Epic Link: PUP-11407 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.428645.1641421059000.13771.1641421080372%40Atlassian.JIRA.
Jira (PUP-11407) Puppet Platform 7.14.0 Release - 2022-01-18
Title: Message Title Eric Griswold created an issue Puppet / PUP-11407 Puppet Platform 7.14.0 Release - 2022-01-18 Issue Type: Epic Assignee: Alex Rodriguez Created: 2022/01/05 2:17 PM Due Date: 2022/01/18 Priority: Normal Reporter: Eric Griswold Puppet Platform 7.14.0 Release - 2022-01-18 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-11412) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.14.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11412 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.14.0) Issue Type: Task Assignee: Alex Rodriguez Created: 2022/01/05 2:17 PM Due Date: 2022/01/17 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2022-01-18) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in #proj-puppet-releases Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PDB-5241) Update winston (PuppetDB 7.6.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5241 Update winston (PuppetDB 7.6.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413100.1629755303000.114437.1629755340716%40Atlassian.JIRA.
Jira (PDB-5236) Merge-up, branch, and create pipelines (PuppetDB 7.6.0)
Title: Message Title
Eric Griswold created an issue
PuppetDB / PDB-5236
Merge-up, branch, and create pipelines (PuppetDB 7.6.0)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2021/08/23 2:48 PM
Due Date:
2021/09/07
Priority:
Normal
Reporter:
Eric Griswold
(Initial planned release date: 2021-09-14) 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-5239) Bump versions, push directly, and tag (PuppetDB 7.6.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5239 Bump versions, push directly, and tag (PuppetDB 7.6.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/08/23 2:48 PM Due Date: 2021/09/10 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) (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-5241) Update winston (PuppetDB 7.6.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5241 Update winston (PuppetDB 7.6.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/08/23 2:48 PM Due Date: 2021/09/15 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PDB-5240) Check builds, promote to PE (PuppetDB 7.6.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5240 Check builds, promote to PE (PuppetDB 7.6.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413098.1629755296000.114435.1629755340625%40Atlassian.JIRA.
Jira (PDB-5240) Check builds, promote to PE (PuppetDB 7.6.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5240 Check builds, promote to PE (PuppetDB 7.6.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/08/23 2:48 PM Due Date: 2021/09/10 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) 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 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. Checkout the branch you promoted to (either the automatic branch like 2018.1.x or the release branch like 2019.8.1-release) of enterprise-dist locally and verify that all platforms have the same tagged version of pe-puppetdb using the below rake command. 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
Jira (PDB-5236) Merge-up, branch, and create pipelines (PuppetDB 7.6.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5236 Merge-up, branch, and create pipelines (PuppetDB 7.6.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413094.1629755281000.114427.1629755340256%40Atlassian.JIRA.
Jira (PDB-5237) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.6.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5237 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.6.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413095.1629755285000.114429.1629755340348%40Atlassian.JIRA.
Jira (PDB-5237) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.6.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5237 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.6.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/08/23 2:48 PM Due Date: 2021/09/07 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) Ensure all tickets referenced in the commit log have 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-5238) Draft release notes (PuppetDB 7.6.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5238 Draft release notes (PuppetDB 7.6.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/08/23 2:48 PM Due Date: 2021/09/12 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) Ensure all tickets have release notes. This query, once you've reconciled the Jira ticket fix versions in the previous step and configured the query with the current release version(s), will identify tickets whose release notes are not complete. Ask your team members to complete any tickets that need release notes (if the ticket's release note is simple you may write release notes for other people's tickets, but you certainly don't have to). Write release notes for the release based on the tickets found in the previous step. One of the simplest ways to gather release notes (once you've completed the step above to ensure every ticket that needs a release note has one) is to use this Jira query be sure to replace the fixVersions with the versions you are releasing and if you don't see release notes you'll need to verify that you're in List View and add the "Release Notes", "Release Notes Summary", and "fixVersion/s" columns to the page. All those view settings are configured in the top right via the two drop-downs below Share, Export, and Tools. Check any tickets for a docs tab with desired information. The release notes go in puppetdb\/documentation\/release_notes.markdown.
Jira (PDB-5239) Bump versions, push directly, and tag (PuppetDB 7.6.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5239 Bump versions, push directly, and tag (PuppetDB 7.6.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413097.1629755292000.114433.1629755340537%40Atlassian.JIRA.
Jira (PDB-5238) Draft release notes (PuppetDB 7.6.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5238 Draft release notes (PuppetDB 7.6.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413096.1629755288000.114431.1629755340448%40Atlassian.JIRA.
Jira (PUP-11228) Communicate scope and timeline of next release (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11228 Communicate scope and timeline of next release (Puppet Platform 7.11.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/08/23 2:47 PM Due Date: 2021/09/15 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) 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-11226) Send release announcement (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11226 Send release announcement (Puppet Platform 7.11.0) Issue Type: Task Assignee: Isaac Hammes Created: 2021/08/23 2:47 PM Due Date: 2021/09/14 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) 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.11.0 is now available".
Jira (PUP-11228) Communicate scope and timeline of next release (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11228 Communicate scope and timeline of next release (Puppet Platform 7.11.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413079.1629755228000.114425.1629755280253%40Atlassian.JIRA.
Jira (PUP-11226) Send release announcement (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11226 Send release announcement (Puppet Platform 7.11.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413077.1629755222000.114421.1629755280218%40Atlassian.JIRA.
Jira (PUP-11227) Update Confluence and JIRA based on release (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11227 Update Confluence and JIRA based on release (Puppet Platform 7.11.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/08/23 2:47 PM Due Date: 2021/09/15 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) 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-11227) Update Confluence and JIRA based on release (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11227 Update Confluence and JIRA based on release (Puppet Platform 7.11.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413078.1629755226000.114423.1629755280235%40Atlassian.JIRA.
Jira (PUP-11224) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11224 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.11.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413074.1629755214000.114417.1629755220712%40Atlassian.JIRA.
Jira (PUP-11225) Publish documentation and updates and release notes (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11225 Publish documentation and updates and release notes (Puppet Platform 7.11.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413075.1629755216000.114419.1629755220764%40Atlassian.JIRA.
Jira (PUP-11219) Puppet Platform 7.11.0 Release - 2021-09-14
Title: Message Title Eric Griswold created an issue Puppet / PUP-11219 Puppet Platform 7.11.0 Release - 2021-09-14 Issue Type: Epic Assignee: Aidan Nathanson Created: 2021/08/23 2:46 PM Due Date: 2021/09/14 Priority: Normal Reporter: Eric Griswold Puppet Platform 7.11.0 Release - 2021-09-14 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11221) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11221 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.11.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/08/23 2:46 PM Due Date: 2021/09/08 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) 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-11223) Prepare release announcement (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11223 Prepare release announcement (Puppet Platform 7.11.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413072.1629755208000.114415.1629755220612%40Atlassian.JIRA.
Jira (PUP-11220) Prepare JIRA and Confluence for release (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11220 Prepare JIRA and Confluence for release (Puppet Platform 7.11.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/08/23 2:46 PM Due Date: 2021/09/08 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) 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.11.0 and puppet-agent 7.11.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PUP-11225) Publish documentation and updates and release notes (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11225 Publish documentation and updates and release notes (Puppet Platform 7.11.0) Issue Type: Task Assignee: Parker Leach Created: 2021/08/23 2:46 PM Due Date: 2021/09/14 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) 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-11222) Prepare documentation updates and release notes (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11222 Prepare documentation updates and release notes (Puppet Platform 7.11.0) Issue Type: Task Assignee: Parker Leach Created: 2021/08/23 2:46 PM Due Date: 2021/09/10 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) 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-11221) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11221 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.11.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413070.1629755203000.114411.1629755220499%40Atlassian.JIRA.
Jira (PUP-11223) Prepare release announcement (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11223 Prepare release announcement (Puppet Platform 7.11.0) Issue Type: Task Assignee: Parker Leach Created: 2021/08/23 2:46 PM Due Date: 2021/09/13 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Parker Leach 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-11220) Prepare JIRA and Confluence for release (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11220 Prepare JIRA and Confluence for release (Puppet Platform 7.11.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413069.1629755198000.114409.1629755220485%40Atlassian.JIRA.
Jira (PUP-11224) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11224 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.11.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/08/23 2:46 PM Due Date: 2021/09/13 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-09-14) 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-11222) Prepare documentation updates and release notes (Puppet Platform 7.11.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11222 Prepare documentation updates and release notes (Puppet Platform 7.11.0) Change By: Eric Griswold Epic Link: PUP-11219 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413071.1629755206000.114413.1629755220555%40Atlassian.JIRA.
Jira (PUP-11141) Prepare documentation updates and release notes (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11141 Prepare documentation updates and release notes (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.405230.1625081268000.70633.1625081280544%40Atlassian.JIRA.
Jira (PDB-5178) Draft release notes (PuppetDB 6.18.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5178 Draft release notes (PuppetDB 6.18.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.405288.1625081536000.70721.1625081580412%40Atlassian.JIRA.
