Jira (PUP-11751) Unable to apply catalog from environment with pcore object types
Title: Message Title Aria Li commented on PUP-11751 Re: Unable to apply catalog from environment with pcore object types I discovered this issue with Josh while working on PUP-11725. So the test I marked as pending and the new one I wrote won't show up until I merge my PR for PUP-11725, I'll link both of them in the ticket description after its merged. 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.480628.167520764.6436.1675207980024%40Atlassian.JIRA.
Jira (PUP-11751) Unable to apply catalog from environment with pcore object types
Title: Message Title Aria Li created an issue Puppet / PUP-11751 Unable to apply catalog from environment with pcore object types Issue Type: Task Assignee: Unassigned Created: 2023/01/31 3:27 PM Priority: Normal Reporter: Aria Li When rich_data is enabled, users should be able to create and use their own rich data type derived from `Object`. However, this test that checks Puppet can apply a catalog from an environment with Pcore object types began failing after enabling strict mode. It seems like there was a warning (when strict was set to warning) before that got swallowed and was never noticed. I'll mark the test as pending for now. I also wrote another test that checks that a catalog can be applied without warnings/errors. Add Comment
Jira (PDB-5586) Bump versions, push directly, and tag (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5586 Bump versions, push directly, and tag (Puppet Platform 7.23.0) Change By: Joshua Partlow Team: Skeletor 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.480625.1675199001000.6432.1675206840044%40Atlassian.JIRA.
Jira (PDB-5588) Update ticket templates (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5588 Update ticket templates (Puppet Platform 7.23.0) Change By: Joshua Partlow Team: Skeletor 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.480627.1675199003000.6434.1675206840142%40Atlassian.JIRA.
Jira (PDB-5587) Check builds, promote to PE (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5587 Check builds, promote to PE (Puppet Platform 7.23.0) Change By: Joshua Partlow Team: Skeletor 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.480626.1675199002000.6433.1675206840095%40Atlassian.JIRA.
Jira (PDB-5584) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5584 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.23.0) Change By: Joshua Partlow Team: Skeletor 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.480623.167519900.6430.1675206780110%40Atlassian.JIRA.
Jira (PDB-5585) Draft release notes (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5585 Draft release notes (Puppet Platform 7.23.0) Change By: Joshua Partlow Team: Skeletor 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.480624.1675199001000.6431.1675206780157%40Atlassian.JIRA.
Jira (PDB-5583) Merge-up, branch, and create pipelines (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5583 Merge-up, branch, and create pipelines (Puppet Platform 7.23.0) Change By: Joshua Partlow Team: Skeletor 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.480622.1675198999000.6429.1675206780045%40Atlassian.JIRA.
Jira (PUP-11740) Puppet Platform 7.23.0 Release - 2023-02-07
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11740 Puppet Platform 7.23.0 Release - 2023-02-07 Change By: Josh Cooper Team/s: Froyo ,Phoenix 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.480596.1675198968000.6384.1675203180028%40Atlassian.JIRA.
Jira (PUP-11714) puppet generate types --all-environments would be nice
Title: Message Title Tony Vu commented on PUP-11714 Re: puppet generate types --all-environments would be nice Pat Riehecky we generally advise people to not deploy --all with r10k as the control repo often has several branches that would be very time consuming to deploy. At this time we don't have many people to work these issues, so unfortunately we will be closing this ticket for now. 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.479098.1673644809000.6378.1675202580022%40Atlassian.JIRA.
Jira (FACT-3178) Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC
Title: Message Title Tony Vu updated an issue Facter / FACT-3178 Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC Change By: Tony Vu Labels: escalation jira_escalated needs-validation 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.479125.1673888594000.6375.1675202160539%40Atlassian.JIRA.
Jira (PUP-11719) ModuleDataProvider::validate_data_hash does not prune hash as advertised
Title: Message Title Tony Vu updated an issue Puppet / PUP-11719 ModuleDataProvider::validate_data_hash does not prune hash as advertised Change By: Tony Vu Labels: needs-validation 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.479277.1674059246000.6354.1675201980023%40Atlassian.JIRA.
Jira (PUP-11724) Unable to target dnfmodule stream named `latest`
Title: Message Title Tony Vu commented on PUP-11724 Re: Unable to target dnfmodule stream named `latest` Thanks for submitting this Pat Riehecky ; we have another ticket, PUP-11588 that is tracking this issue. I'm going to close this one out and feel free to follow that one to track its progress. 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.479508.1674582615000.6348.1675201200138%40Atlassian.JIRA.
Jira (FACT-3180) Facter mixes up OracleLinux and Redhat
Title: Message Title Tony Vu updated an issue Facter / FACT-3180 Facter mixes up OracleLinux and Redhat Change By: Tony Vu Team: Phoenix 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.479622.1674731331000.6345.1675201080109%40Atlassian.JIRA.
Jira (PDB-5585) Draft release notes (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5585 Draft release notes (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480624.1675199001000.6302.1675199040369%40Atlassian.JIRA.
Jira (PDB-5586) Bump versions, push directly, and tag (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5586 Bump versions, push directly, and tag (Puppet Platform 7.23.0) Issue Type: Task Assignee: Joshua Partlow Created: 2023/01/31 1:03 PM Due Date: 2023/02/03 Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) (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. Run the `tag-release` command: Change to a clean checkout of the relevant `puppetdb` branch (e.g. 6.x, main, ...). Run the `tag-release` script. This
Jira (PDB-5588) Update ticket templates (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5588 Update ticket templates (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480627.1675199003000.6308.1675199040657%40Atlassian.JIRA.
Jira (PDB-5588) Update ticket templates (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5588 Update ticket templates (Puppet Platform 7.23.0) Issue Type: Task Assignee: Joshua Partlow Created: 2023/01/31 1:03 PM Due Date: 2023/02/08 Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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.11#820011-sha1:0629dd8)
Jira (PDB-5584) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5584 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480623.167519900.6300.1675199040274%40Atlassian.JIRA.
Jira (PDB-5583) Merge-up, branch, and create pipelines (Puppet Platform 7.23.0)
Title: Message Title
tefoji created an issue
PuppetDB / PDB-5583
Merge-up, branch, and create pipelines (Puppet Platform 7.23.0)
Issue Type:
Task
Assignee:
Joshua Partlow
Created:
2023/01/31 1:03 PM
Due Date:
2023/01/31
Priority:
Normal
Reporter:
tefoji
(Initial planned release date: 2023-02-07) 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. 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). Then, prepare the branch for release:
If needed, create the branch (off of main, almost certainly)
Jira (PDB-5584) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5584 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.23.0) Issue Type: Task Assignee: Joshua Partlow Created: 2023/01/31 1:03 PM Due Date: 2023/01/31 Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-5587) Check builds, promote to PE (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5587 Check builds, promote to PE (Puppet Platform 7.23.0) Issue Type: Task Assignee: Joshua Partlow Created: 2023/01/31 1:03 PM Due Date: 2023/02/03 Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) Check that all the builds are green. The parameterized acceptance tests' upgrade_latest jobs in Jenkins are expected to fail at this point with an error like: Error: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install puppetdb-7.11.0-1.el7' returned 1: Error: Nothing to do Choose the tab for your branch over at https://jenkins-enterprise.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 an enterprise-dist release branch has already been cut, rebuild the package
Jira (PDB-5586) Bump versions, push directly, and tag (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5586 Bump versions, push directly, and tag (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480625.1675199001000.6304.1675199040465%40Atlassian.JIRA.
Jira (PDB-5583) Merge-up, branch, and create pipelines (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5583 Merge-up, branch, and create pipelines (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480622.1675198999000.6298.1675199040178%40Atlassian.JIRA.
Jira (PDB-5587) Check builds, promote to PE (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5587 Check builds, promote to PE (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480626.1675199002000.6306.1675199040562%40Atlassian.JIRA.
Jira (PDB-5585) Draft release notes (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5585 Draft release notes (Puppet Platform 7.23.0) Issue Type: Task Assignee: Joshua Partlow Created: 2023/01/31 1:03 PM Due Date: 2023/02/05 Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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. Request review from the docs team by pinging @heston in the opened PR, at least one day before Ready to Ship
Jira (PUP-11741) Prepare JIRA and Confluence for release (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11741 Prepare JIRA and Confluence for release (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 1:02 PM Due Date: 2023/02/01 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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.23.0 and puppet-agent 7.23.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to reference the
Jira (PUP-11746) Publish documentation and updates and release notes (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11746 Publish documentation and updates and release notes (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480603.1675198975000.6288.1675198980866%40Atlassian.JIRA.
Jira (PUP-11749) Update Confluence and JIRA based on release (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11749 Update Confluence and JIRA based on release (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480607.1675198978000.6294.1675198981154%40Atlassian.JIRA.
Jira (PUP-11744) Prepare release announcement (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11744 Prepare release announcement (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 1:02 PM Due Date: 2023/02/06 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11746) Publish documentation and updates and release notes (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11746 Publish documentation and updates and release notes (Puppet Platform 7.23.0) Issue Type: Task Assignee: Parker Leach Created: 2023/01/31 1:02 PM Due Date: 2023/02/07 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11747) Send release announcement (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11747 Send release announcement (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480605.1675198977000.6290.1675198980962%40Atlassian.JIRA.
Jira (PUP-11747) Send release announcement (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11747 Send release announcement (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 1:02 PM Due Date: 2023/02/07 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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.23.0 is now available"
Jira (PUP-11748) Schedule a retrospective (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11748 Schedule a retrospective (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480606.1675198977000.6292.1675198981057%40Atlassian.JIRA.
Jira (PUP-11742) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11742 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 1:02 PM Due Date: 2023/02/01 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11749) Update Confluence and JIRA based on release (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11749 Update Confluence and JIRA based on release (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 1:02 PM Due Date: 2023/02/09 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the description and
Jira (PUP-11750) Communicate scope and timeline of next release (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11750 Communicate scope and timeline of next release (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480608.1675198979000.6296.1675198981249%40Atlassian.JIRA.
Jira (PUP-11745) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11745 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 1:02 PM Due Date: 2023/02/06 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11748) Schedule a retrospective (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11748 Schedule a retrospective (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 1:02 PM Due Date: 2023/02/07 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) Schedule a retrospective for this release. This should happen as soon as possible after the release, so that details are fresh in our heads. Ensure all current release leads are invited and that the Trello board is shared with them. Eric Griswold Parker Leach Christopher Thorn Eric Newton Joshua Partlow Add Comment
Jira (PUP-11741) Prepare JIRA and Confluence for release (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11741 Prepare JIRA and Confluence for release (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480597.1675198969000.6278.1675198980382%40Atlassian.JIRA.
Jira (PUP-11744) Prepare release announcement (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11744 Prepare release announcement (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480600.1675198973000.6284.1675198980670%40Atlassian.JIRA.
Jira (PUP-11742) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11742 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480598.1675198972000.6280.1675198980478%40Atlassian.JIRA.
Jira (PUP-11743) Prepare documentation updates and release notes (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11743 Prepare documentation updates and release notes (Puppet Platform 7.23.0) Issue Type: Task Assignee: Parker Leach Created: 2023/01/31 1:02 PM Due Date: 2023/02/03 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11750) Communicate scope and timeline of next release (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11750 Communicate scope and timeline of next release (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 1:02 PM Due Date: 2023/02/09 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11745) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11745 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480602.1675198974000.6286.1675198980770%40Atlassian.JIRA.
Jira (PUP-11743) Prepare documentation updates and release notes (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11743 Prepare documentation updates and release notes (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11740 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.480599.1675198972000.6282.1675198980573%40Atlassian.JIRA.
Jira (PUP-11740) Puppet Platform 7.23.0 Release - 2023-02-07
Title: Message Title tefoji created an issue Puppet / PUP-11740 Puppet Platform 7.23.0 Release - 2023-02-07 Issue Type: Epic Assignee: Mae Caballes Created: 2023/01/31 1:02 PM Due Date: 2023/02/07 Priority: Normal Reporter: tefoji Puppet Platform 7.23.0 Release - 2023-02-07 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11737) Schedule a retrospective (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11737 Schedule a retrospective (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 12:47 PM Due Date: 2023/02/07 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) Schedule a retrospective for this release. This should happen as soon as possible after the release, so that details are fresh in our heads. Ensure all current release leads are invited and that the Trello board is shared with them. Eric Griswold Parker Leach Christopher Thorn Eric Newton [~josh.partlow] Add
Jira (PUP-11739) Communicate scope and timeline of next release (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11739 Communicate scope and timeline of next release (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 12:47 PM Due Date: 2023/02/09 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11738) Update Confluence and JIRA based on release (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11738 Update Confluence and JIRA based on release (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 12:47 PM Due Date: 2023/02/09 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the description and
Jira (PUP-11735) Publish documentation and updates and release notes (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11735 Publish documentation and updates and release notes (Puppet Platform 7.23.0) Issue Type: Task Assignee: Parker Leach Created: 2023/01/31 12:47 PM Due Date: 2023/02/07 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11735) Publish documentation and updates and release notes (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11735 Publish documentation and updates and release notes (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11729 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.480577.1675198033000.6241.1675198080868%40Atlassian.JIRA.
Jira (PUP-11734) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11734 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 12:47 PM Due Date: 2023/02/06 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11737) Schedule a retrospective (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11737 Schedule a retrospective (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11729 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.480580.1675198035000.6245.1675198081058%40Atlassian.JIRA.
Jira (PUP-11736) Send release announcement (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11736 Send release announcement (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11729 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.480579.1675198035000.6243.1675198080962%40Atlassian.JIRA.
Jira (PUP-11731) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11731 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11729 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.480572.167519803.6233.1675198080477%40Atlassian.JIRA.
Jira (PUP-11734) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11734 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11729 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.480576.1675198033000.6239.1675198080765%40Atlassian.JIRA.
Jira (PUP-11731) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11731 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 12:47 PM Due Date: 2023/02/01 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11736) Send release announcement (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11736 Send release announcement (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 12:47 PM Due Date: 2023/02/07 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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.23.0 is now available"
Jira (PUP-11733) Prepare release announcement (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11733 Prepare release announcement (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 12:47 PM Due Date: 2023/02/06 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11733) Prepare release announcement (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11733 Prepare release announcement (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11729 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.480574.1675198031000.6237.1675198080669%40Atlassian.JIRA.
Jira (PUP-11739) Communicate scope and timeline of next release (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11739 Communicate scope and timeline of next release (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11729 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.480582.1675198037000.6249.1675198081262%40Atlassian.JIRA.
Jira (PUP-11730) Prepare JIRA and Confluence for release (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11730 Prepare JIRA and Confluence for release (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11729 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.480571.1675198029000.6231.1675198080381%40Atlassian.JIRA.
Jira (PUP-11732) Prepare documentation updates and release notes (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11732 Prepare documentation updates and release notes (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11729 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.480573.1675198031000.6235.1675198080573%40Atlassian.JIRA.
Jira (PUP-11730) Prepare JIRA and Confluence for release (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11730 Prepare JIRA and Confluence for release (Puppet Platform 7.23.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/31 12:47 PM Due Date: 2023/02/01 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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.23.0 and puppet-agent 7.23.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to reference the
Jira (PUP-11738) Update Confluence and JIRA based on release (Puppet Platform 7.23.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11738 Update Confluence and JIRA based on release (Puppet Platform 7.23.0) Change By: tefoji Epic Link: PUP-11729 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.480581.1675198036000.6247.1675198081161%40Atlassian.JIRA.
Jira (PUP-11729) Puppet Platform 7.23.0 Release - 2023-02-07
Title: Message Title tefoji created an issue Puppet / PUP-11729 Puppet Platform 7.23.0 Release - 2023-02-07 Issue Type: Epic Assignee: Mae Caballes Created: 2023/01/31 12:47 PM Due Date: 2023/02/07 Priority: Normal Reporter: tefoji Puppet Platform 7.23.0 Release - 2023-02-07 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11732) Prepare documentation updates and release notes (Puppet Platform 7.23.0)
Title: Message Title tefoji created an issue Puppet / PUP-11732 Prepare documentation updates and release notes (Puppet Platform 7.23.0) Issue Type: Task Assignee: Parker Leach Created: 2023/01/31 12:47 PM Due Date: 2023/02/03 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11728) Puppet agent ignore splay when runinterval is lowered
Title: Message Title Steve Jones created an issue Puppet / PUP-11728 Puppet agent ignore splay when runinterval is lowered Issue Type: Bug Affects Versions: PUP 7.18.0 Assignee: Unassigned Created: 2023/01/31 10:56 AM Priority: Normal Reporter: Steve Jones Puppet Version: 7.18.0 Puppet Server Version: 2021.7.0.16 OS Name/Version: Oracle Linux 7 When lowering runinterval on agents, from 60m to 30m for example, splay on, and splaylimit set to runinterval, agents quicker trigger a run and ignore the splay setting. We use the puppet_conf bolt task to make agent config changes, so a large group of agents suddenly synchronize and stay that way when we update their runintervals on disk. Restarting agents resolves the issue because the splay setting will be used. We run into this because sometimes we set runinterval to a higher value when we think we have performance problems on the compilers or primary server. Reverting the setting then causes this issue, which causes performance problems To reproduce: bolt task run puppet_conf action="" setting=splay section=agent value=true bolt task run puppet_conf action="" setting=splaylimit section=agent value=10m bolt task run puppet_conf action="" setting=runinterval section=agent value=10m They're synchronized now, the fix is restarting all the agents. That's not bad, but I don't see the benefit to having the agent reread the puppet.conf every few seconds if it can't handle an updated runinterval properly. Desired Behavior: I would expect it the agent schedule to work similarly to as if I had just restarted the agent. Actual Behavior: Agents stack up and run simultaneously.
Jira (PUP-11727) Restrictive umask on compiler causes errors after upgrade
Title: Message Title Charmaine Pritchett updated an issue Puppet / PUP-11727 Restrictive umask on compiler causes errors after upgrade Change By: Charmaine Pritchett Labels: jira_escalated 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.480541.1675183947000.6142.1675184040082%40Atlassian.JIRA.
Jira (PUP-11727) Restrictive umask on compiler causes errors after upgrade
Title: Message Title Charmaine Pritchett updated an issue Puppet / PUP-11727 Restrictive umask on compiler causes errors after upgrade Change By: Charmaine Pritchett Zendesk Ticket Count: 1 Zendesk Ticket IDs: 50900 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.480541.1675183947000.6141.1675184040030%40Atlassian.JIRA.
Jira (PUP-11727) Restrictive umask on compiler causes errors after upgrade
Title: Message Title Aaron Hilton created an issue Puppet / PUP-11727 Restrictive umask on compiler causes errors after upgrade Issue Type: Improvement Affects Versions: PUP 7.21.0 Assignee: Unassigned Components: Compiler Created: 2023/01/31 8:52 AM Environment: RHEL 7 PE 2023.0 Priority: Normal Reporter: Aaron Hilton Customer upgraded from 2021.7.1 to 2023.0 and all compilers except one were reporting as operational in the Console GUI except one. Running puppet infra status came back with no issues for affected compiler and all services were running on the compiler. The puppetserver.log file on the affected compiler was flooded with the error Facter Error loading fact /opt/puppetlabs/puppet/cache/lib/facter/pe_postgresql_info.rb: no such file to load -- /opt/puppetlabs/puppet/cache/lib/pe_install/pe_postgresql_info.rb Further investigation found that the parent directories of these files did not have sufficient permissions for the pe-puppet user to access them causing the error.
Jira (PUP-11660) Puppet Maintenance CY23 Q3
Title: Message Title Lisa Ross updated an issue Puppet / PUP-11660 Puppet Maintenance CY23 Q3 Change By: Lisa Ross Labels: 23Q3 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.472735.1666288019000.6051.1675161120236%40Atlassian.JIRA.
