Jira (PDB-5271) Merge-up, branch, and create pipelines (PuppetDB 6.19.0)
Title: Message Title
Isaac Hammes created an issue
PuppetDB / PDB-5271
Merge-up, branch, and create pipelines (PuppetDB 6.19.0)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2021/09/16 2:38 PM
Due Date:
2021/09/29
Priority:
Normal
Reporter:
Isaac Hammes
(Initial planned release date: 2021-10-12) 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-5273) Draft release notes (PuppetDB 6.19.0)
Title: Message Title Isaac Hammes created an issue PuppetDB / PDB-5273 Draft release notes (PuppetDB 6.19.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/09/16 2:38 PM Due Date: 2021/10/10 Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-5275) Check builds, promote to PE (PuppetDB 6.19.0)
Title: Message Title Isaac Hammes updated an issue PuppetDB / PDB-5275 Check builds, promote to PE (PuppetDB 6.19.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416151.1631828301000.132002.1631828340592%40Atlassian.JIRA.
Jira (PDB-5275) Check builds, promote to PE (PuppetDB 6.19.0)
Title: Message Title Isaac Hammes created an issue PuppetDB / PDB-5275 Check builds, promote to PE (PuppetDB 6.19.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/09/16 2:38 PM Due Date: 2021/10/02 Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-5273) Draft release notes (PuppetDB 6.19.0)
Title: Message Title Isaac Hammes updated an issue PuppetDB / PDB-5273 Draft release notes (PuppetDB 6.19.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416149.1631828292000.131998.1631828340417%40Atlassian.JIRA.
Jira (PDB-5274) Bump versions, push directly, and tag (PuppetDB 6.19.0)
Title: Message Title Isaac Hammes created an issue PuppetDB / PDB-5274 Bump versions, push directly, and tag (PuppetDB 6.19.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/09/16 2:38 PM Due Date: 2021/10/02 Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) (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-5272) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.19.0)
Title: Message Title Isaac Hammes created an issue PuppetDB / PDB-5272 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.19.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/09/16 2:38 PM Due Date: 2021/09/29 Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-5276) Update winston (PuppetDB 6.19.0)
Title: Message Title Isaac Hammes created an issue PuppetDB / PDB-5276 Update winston (PuppetDB 6.19.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/09/16 2:38 PM Due Date: 2021/10/13 Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-5272) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.19.0)
Title: Message Title Isaac Hammes updated an issue PuppetDB / PDB-5272 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.19.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416148.1631828288000.131996.1631828340330%40Atlassian.JIRA.
Jira (PDB-5271) Merge-up, branch, and create pipelines (PuppetDB 6.19.0)
Title: Message Title Isaac Hammes updated an issue PuppetDB / PDB-5271 Merge-up, branch, and create pipelines (PuppetDB 6.19.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416147.1631828281000.131994.1631828340241%40Atlassian.JIRA.
Jira (PDB-5276) Update winston (PuppetDB 6.19.0)
Title: Message Title Isaac Hammes updated an issue PuppetDB / PDB-5276 Update winston (PuppetDB 6.19.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416153.1631828312000.132004.1631828340680%40Atlassian.JIRA.
Jira (PDB-5274) Bump versions, push directly, and tag (PuppetDB 6.19.0)
Title: Message Title Isaac Hammes updated an issue PuppetDB / PDB-5274 Bump versions, push directly, and tag (PuppetDB 6.19.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416150.1631828297000.132000.1631828340505%40Atlassian.JIRA.
Jira (PUP-11262) Communicate scope and timeline of next release (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11262 Communicate scope and timeline of next release (Puppet Platform 6.25.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416132.1631828219000.131992.1631828280345%40Atlassian.JIRA.
Jira (PUP-11261) Update Confluence and JIRA based on release (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11261 Update Confluence and JIRA based on release (Puppet Platform 6.25.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/09/16 2:36 PM Due Date: 2021/10/13 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-11259) Publish documentation and updates and release notes (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11259 Publish documentation and updates and release notes (Puppet Platform 6.25.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416127.1631828204000.131981.1631828220988%40Atlassian.JIRA.
Jira (PUP-11256) Prepare documentation updates and release notes (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11256 Prepare documentation updates and release notes (Puppet Platform 6.25.0) Issue Type: Task Assignee: Parker Leach Created: 2021/09/16 2:36 PM Due Date: 2021/10/02 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-11254) Prepare JIRA and Confluence for release (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11254 Prepare JIRA and Confluence for release (Puppet Platform 6.25.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416121.1631828181000.131971.1631828220541%40Atlassian.JIRA.
Jira (PUP-11257) Prepare release announcement (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11257 Prepare release announcement (Puppet Platform 6.25.0) Issue Type: Task Assignee: Parker Leach Created: 2021/09/16 2:36 PM Due Date: 2021/10/11 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-11258) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11258 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.25.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416126.1631828198000.131979.1631828220900%40Atlassian.JIRA.
Jira (PUP-11258) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11258 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.25.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/09/16 2:36 PM Due Date: 2021/10/11 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-11262) Communicate scope and timeline of next release (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11262 Communicate scope and timeline of next release (Puppet Platform 6.25.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/09/16 2:36 PM Due Date: 2021/10/13 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-11259) Publish documentation and updates and release notes (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11259 Publish documentation and updates and release notes (Puppet Platform 6.25.0) Issue Type: Task Assignee: Parker Leach Created: 2021/09/16 2:36 PM Due Date: 2021/10/12 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-11261) Update Confluence and JIRA based on release (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11261 Update Confluence and JIRA based on release (Puppet Platform 6.25.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416131.1631828216000.131985.1631828221168%40Atlassian.JIRA.
Jira (PUP-11260) Send release announcement (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11260 Send release announcement (Puppet Platform 6.25.0) Issue Type: Task Assignee: Isaac Hammes Created: 2021/09/16 2:36 PM Due Date: 2021/10/12 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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.25.0 is now available".
Jira (PUP-11260) Send release announcement (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11260 Send release announcement (Puppet Platform 6.25.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416129.1631828211000.131983.1631828221077%40Atlassian.JIRA.
Jira (PUP-11256) Prepare documentation updates and release notes (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11256 Prepare documentation updates and release notes (Puppet Platform 6.25.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416123.1631828188000.131975.1631828220717%40Atlassian.JIRA.
Jira (PUP-11253) Puppet Platform 6.25.0 Release - 2021-10-12
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11253 Puppet Platform 6.25.0 Release - 2021-10-12 Issue Type: Epic Assignee: Aidan Nathanson Created: 2021/09/16 2:36 PM Due Date: 2021/10/12 Priority: Normal Reporter: Isaac Hammes Puppet Platform 6.25.0 Release - 2021-10-12 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11257) Prepare release announcement (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11257 Prepare release announcement (Puppet Platform 6.25.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416124.1631828192000.131977.1631828220805%40Atlassian.JIRA.
Jira (PUP-11255) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11255 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.25.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/09/16 2:36 PM Due Date: 2021/09/30 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-11254) Prepare JIRA and Confluence for release (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11254 Prepare JIRA and Confluence for release (Puppet Platform 6.25.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/09/16 2:36 PM Due Date: 2021/09/30 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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.25.0 and puppet-agent 6.25.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-11255) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.25.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11255 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.25.0) Change By: Isaac Hammes Epic Link: PUP-11253 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.416122.1631828185000.131973.1631828220629%40Atlassian.JIRA.
Jira (PDB-5265) Merge-up, branch, and create pipelines (PuppetDB 7.7.0)
Title: Message Title Isaac Hammes updated an issue PuppetDB / PDB-5265 Merge-up, branch, and create pipelines (PuppetDB 7.7.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416111.1631827664000.131914.1631827680237%40Atlassian.JIRA.
Jira (PDB-5266) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.7.0)
Title: Message Title Isaac Hammes created an issue PuppetDB / PDB-5266 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.7.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/09/16 2:27 PM Due Date: 2021/09/30 Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-5269) Check builds, promote to PE (PuppetDB 7.7.0)
Title: Message Title Isaac Hammes created an issue PuppetDB / PDB-5269 Check builds, promote to PE (PuppetDB 7.7.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/09/16 2:28 PM Due Date: 2021/10/03 Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-5269) Check builds, promote to PE (PuppetDB 7.7.0)
Title: Message Title Isaac Hammes updated an issue PuppetDB / PDB-5269 Check builds, promote to PE (PuppetDB 7.7.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416115.1631827682000.131934.1631827740952%40Atlassian.JIRA.
Jira (PDB-5270) Update winston (PuppetDB 7.7.0)
Title: Message Title Isaac Hammes updated an issue PuppetDB / PDB-5270 Update winston (PuppetDB 7.7.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416117.1631827694000.131936.1631827741044%40Atlassian.JIRA.
Jira (PDB-5268) Bump versions, push directly, and tag (PuppetDB 7.7.0)
Title: Message Title Isaac Hammes updated an issue PuppetDB / PDB-5268 Bump versions, push directly, and tag (PuppetDB 7.7.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416114.1631827678000.131932.1631827740862%40Atlassian.JIRA.
Jira (PDB-5270) Update winston (PuppetDB 7.7.0)
Title: Message Title Isaac Hammes created an issue PuppetDB / PDB-5270 Update winston (PuppetDB 7.7.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/09/16 2:28 PM Due Date: 2021/10/13 Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-5267) Draft release notes (PuppetDB 7.7.0)
Title: Message Title Isaac Hammes created an issue PuppetDB / PDB-5267 Draft release notes (PuppetDB 7.7.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/09/16 2:27 PM Due Date: 2021/10/10 Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-5265) Merge-up, branch, and create pipelines (PuppetDB 7.7.0)
Title: Message Title
Isaac Hammes created an issue
PuppetDB / PDB-5265
Merge-up, branch, and create pipelines (PuppetDB 7.7.0)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2021/09/16 2:27 PM
Due Date:
2021/09/30
Priority:
Normal
Reporter:
Isaac Hammes
(Initial planned release date: 2021-10-12) 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-5268) Bump versions, push directly, and tag (PuppetDB 7.7.0)
Title: Message Title Isaac Hammes created an issue PuppetDB / PDB-5268 Bump versions, push directly, and tag (PuppetDB 7.7.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/09/16 2:27 PM Due Date: 2021/10/03 Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) (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-5267) Draft release notes (PuppetDB 7.7.0)
Title: Message Title Isaac Hammes updated an issue PuppetDB / PDB-5267 Draft release notes (PuppetDB 7.7.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416113.1631827674000.131918.1631827680425%40Atlassian.JIRA.
Jira (PDB-5266) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.7.0)
Title: Message Title Isaac Hammes updated an issue PuppetDB / PDB-5266 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.7.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416112.1631827669000.131916.1631827680333%40Atlassian.JIRA.
Jira (PUP-11246) Prepare documentation updates and release notes (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11246 Prepare documentation updates and release notes (Puppet Platform 7.12.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416088.1631827577000.131898.1631827620504%40Atlassian.JIRA.
Jira (PUP-11245) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11245 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.12.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/09/16 2:26 PM Due Date: 2021/10/01 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-11251) Update Confluence and JIRA based on release (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11251 Update Confluence and JIRA based on release (Puppet Platform 7.12.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416095.163182760.131908.1631827620877%40Atlassian.JIRA.
Jira (PUP-11245) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11245 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.12.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416087.1631827574000.131896.1631827620452%40Atlassian.JIRA.
Jira (PUP-11250) Send release announcement (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11250 Send release announcement (Puppet Platform 7.12.0) Issue Type: Task Assignee: Isaac Hammes Created: 2021/09/16 2:26 PM Due Date: 2021/10/12 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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.12.0 is now available".
Jira (PUP-11247) Prepare release announcement (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11247 Prepare release announcement (Puppet Platform 7.12.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416089.163182758.131900.1631827620518%40Atlassian.JIRA.
Jira (PUP-11250) Send release announcement (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11250 Send release announcement (Puppet Platform 7.12.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416094.1631827596000.131906.1631827620788%40Atlassian.JIRA.
Jira (PUP-11249) Publish documentation and updates and release notes (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11249 Publish documentation and updates and release notes (Puppet Platform 7.12.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416092.163182759.131904.1631827620701%40Atlassian.JIRA.
Jira (PUP-11252) Communicate scope and timeline of next release (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11252 Communicate scope and timeline of next release (Puppet Platform 7.12.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416096.1631827603000.131910.1631827620984%40Atlassian.JIRA.
Jira (PUP-11244) Prepare JIRA and Confluence for release (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11244 Prepare JIRA and Confluence for release (Puppet Platform 7.12.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/09/16 2:26 PM Due Date: 2021/10/01 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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.12.0 and puppet-agent 7.12.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-11247) Prepare release announcement (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11247 Prepare release announcement (Puppet Platform 7.12.0) Issue Type: Task Assignee: Parker Leach Created: 2021/09/16 2:26 PM Due Date: 2021/10/11 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-11249) Publish documentation and updates and release notes (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11249 Publish documentation and updates and release notes (Puppet Platform 7.12.0) Issue Type: Task Assignee: Parker Leach Created: 2021/09/16 2:26 PM Due Date: 2021/10/12 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-11248) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11248 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.12.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416091.1631827587000.131902.1631827620608%40Atlassian.JIRA.
Jira (PUP-11246) Prepare documentation updates and release notes (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11246 Prepare documentation updates and release notes (Puppet Platform 7.12.0) Issue Type: Task Assignee: Parker Leach Created: 2021/09/16 2:26 PM Due Date: 2021/10/03 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-11251) Update Confluence and JIRA based on release (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11251 Update Confluence and JIRA based on release (Puppet Platform 7.12.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/09/16 2:26 PM Due Date: 2021/10/13 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-11244) Prepare JIRA and Confluence for release (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes updated an issue Puppet / PUP-11244 Prepare JIRA and Confluence for release (Puppet Platform 7.12.0) Change By: Isaac Hammes Epic Link: PUP-11243 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.416086.1631827571000.131894.1631827620401%40Atlassian.JIRA.
Jira (PUP-11243) Puppet Platform 7.12.0 Release - 2021-10-12
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11243 Puppet Platform 7.12.0 Release - 2021-10-12 Issue Type: Epic Assignee: Aidan Nathanson Created: 2021/09/16 2:26 PM Due Date: 2021/10/12 Priority: Normal Reporter: Isaac Hammes Puppet Platform 7.12.0 Release - 2021-10-12 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11248) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11248 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.12.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/09/16 2:26 PM Due Date: 2021/10/11 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 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-11252) Communicate scope and timeline of next release (Puppet Platform 7.12.0)
Title: Message Title Isaac Hammes created an issue Puppet / PUP-11252 Communicate scope and timeline of next release (Puppet Platform 7.12.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/09/16 2:26 PM Due Date: 2021/10/13 Labels: release Priority: Normal Reporter: Isaac Hammes (Initial planned release date: 2021-10-12) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PDB-5216) Add optional query origin field
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5216 Add optional query origin field Change By: Austin Blatt Release Notes: New Feature Release Notes Summary: New query origin field 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.408854.1627502694000.131775.1631824980034%40Atlassian.JIRA.
Jira (PUP-11106) superclass mismatch for class Uniquefile (TypeError)
Title: Message Title
Josh Cooper commented on PUP-11106
Re: superclass mismatch for class Uniquefile (TypeError)
So there's an easy way to reproduce the issue:
# mkdir -p /tmp/realpath/lib
# cat < /tmp/realpath/lib/a.rb
require_relative 'b'
puts load('/tmp/link/lib/b.rb')
END
# cat < /tmp/realpath/lib/b.rb
require_relative 'c'
END
# cat < /tmp/realpath/lib/c.rb
require 'tempfile'
class C < DelegateClass(File); end
END
# ln -s /tmp/realpath/ /tmp/link
The following works using system ruby:
Jira (PUP-11235) versioncmp() thinks 11.0 is greater than 11
Title: Message Title Josh Cooper commented on PUP-11235 Re: versioncmp() thinks 11.0 is greater than 11 One thing I remembered is many packages don't follow SemVer. For example, we ran into issues while adding ensure => '> 1.0.0' for package resources in PUP-10298, PUP-10416, etc. For this issue, it might be worth just solving the general problem of implicit 0 minor and/or patch components. 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.413995.1630486051000.131575.1631812920052%40Atlassian.JIRA.
Jira (FACT-3067) Facter API does not resolve custom facts that partial match legacy facts
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3067 Facter API does not resolve custom facts that partial match legacy facts Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: Before this fix, custom facts with names that partially matched core legacy facts were being resolved as expected in CLI but not using the API. Due to the nature of how legacy facts are defined in Facter 4, with the regular _expression_ used in FACT_NAME, `Facter::FactManager` was not resolving custom facts if core or external facts had any results.This fix adds a new method to check if the user query matches the name of already resolved facts to decide whether or not custom facts should be also resolved. 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
Jira (PUP-11242) Update Public-facing Puppet docs to include AlmaLinux 8(x86_64)
Title: Message Title Ciprian Badescu created an issue Puppet / PUP-11242 Update Public-facing Puppet docs to include AlmaLinux 8(x86_64) Issue Type: Task Assignee: Unassigned Created: 2021/09/16 5:27 AM Priority: Normal Reporter: Ciprian Badescu Update Public-facing Puppet docs to include this platform This ticket will be set with the fix version of the first release containing the new platform and checked with doc team during the Platform release process. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11242) Update Public-facing Puppet docs to include AlmaLinux 8(x86_64)
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11242 Update Public-facing Puppet docs to include AlmaLinux 8(x86_64) Change By: Ciprian Badescu Epic Link: PA-4002 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.415901.1631795237000.131276.1631795280176%40Atlassian.JIRA.
Jira (PUP-11223) Prepare release announcement (Puppet Platform 7.11.0)
Title: Message Title Claire Cadman commented on PUP-11223 Re: Prepare release announcement (Puppet Platform 7.11.0) Maggie Dreyer Austin Blatt Please add any server or PuppetDB changes that you want to call out to the highlights above. Thanks! 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.131272.1631795220027%40Atlassian.JIRA.
Jira (PUP-11223) Prepare release announcement (Puppet Platform 7.11.0)
Title: Message Title Claire Cadman assigned an issue to Claire Cadman Puppet / PUP-11223 Prepare release announcement (Puppet Platform 7.11.0) Change By: Claire Cadman Assignee: Parker Leach Claire Cadman 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.131271.1631795160085%40Atlassian.JIRA.
Jira (PUP-11223) Prepare release announcement (Puppet Platform 7.11.0)
Title: Message Title Claire Cadman commented on PUP-11223 Re: Prepare release announcement (Puppet Platform 7.11.0) The next release in the Puppet 7 series, Puppet 7.11.0, is now available! The release contains new features, minor enhancements, and bug fixes including: Support for Ubuntu 18.04 aarch64 10% lower memory consumption during catalog compilation Support for multiple Facter implementations Updates to OpenSSL For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/latest/release_notes_osp.html 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.131269.1631795100035%40Atlassian.JIRA.
Jira (PUP-11225) Publish documentation and updates and release notes (Puppet Platform 7.11.0)
Title: Message Title Claire Cadman assigned an issue to Claire Cadman Puppet / PUP-11225 Publish documentation and updates and release notes (Puppet Platform 7.11.0) Change By: Claire Cadman Assignee: Parker Leach Claire Cadman 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.131268.1631795040126%40Atlassian.JIRA.
Jira (PUP-11222) Prepare documentation updates and release notes (Puppet Platform 7.11.0)
Title: Message Title Claire Cadman commented on PUP-11222 Re: Prepare documentation updates and release notes (Puppet Platform 7.11.0) Release notes draft: https://docs-herrera-preview.netlify.app/docs/puppet/7/release_notes_puppet.html#release_notes_puppet 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.131264.1631794920028%40Atlassian.JIRA.
Jira (PUP-11222) Prepare documentation updates and release notes (Puppet Platform 7.11.0)
Title: Message Title Claire Cadman assigned an issue to Claire Cadman Puppet / PUP-11222 Prepare documentation updates and release notes (Puppet Platform 7.11.0) Change By: Claire Cadman Assignee: Parker Leach Claire Cadman 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.131263.1631794860030%40Atlassian.JIRA.
Jira (PUP-11223) Prepare release announcement (Puppet Platform 7.11.0)
Title: Message Title Ciprian Badescu commented on PUP-11223 Re: Prepare release announcement (Puppet Platform 7.11.0) Agent shout out: support for Ubuntu 18.04 aarch64 lowers memory consumption during catalog compilation up to 10% puppet now supports multiple Facter implementations OpenSSL update 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.131261.1631794140026%40Atlassian.JIRA.
Jira (PDB-5264) Create a cd4pe deployment and link it to PE
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5264 Create a cd4pe deployment and link it to PE Change By: Bogdan Irimie Determine how cd4pe and PE/puppetdb interact.Deploy cd4pe in a test environment and link it to a PE deployment. 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.415874.1631792786000.131256.1631792880030%40Atlassian.JIRA.
Jira (PDB-5264) Create a cd4pe deployment and link it to PE
Title: Message Title Bogdan Irimie created an issue PuppetDB / PDB-5264 Create a cd4pe deployment and link it to PE Issue Type: Task Assignee: Unassigned Created: 2021/09/16 4:46 AM Priority: Normal Reporter: Bogdan Irimie 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
Jira (PDB-5263) Determine how cd4pe interacts with PuppetDB
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5263 Determine how cd4pe interacts with PuppetDB Change By: Bogdan Irimie Team/s: Ghost 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.415873.1631792086000.131254.1631792760044%40Atlassian.JIRA.
Jira (PDB-5263) Determine how cd4pe interacts with PuppetDB
Title: Message Title Bogdan Irimie created an issue PuppetDB / PDB-5263 Determine how cd4pe interacts with PuppetDB Issue Type: Epic Assignee: Unassigned Created: 2021/09/16 4:34 AM Priority: Normal Reporter: Bogdan Irimie 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
Jira (FACT-3073) Inconsistencies to set Facter::Core::Execution.execute timeout
Title: Message Title Luchian Nemes assigned an issue to Gabriel Nagy Facter / FACT-3073 Inconsistencies to set Facter::Core::Execution.execute timeout Change By: Luchian Nemes Assignee: Gabriel Nagy 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.415028.1631164898000.131220.1631791200184%40Atlassian.JIRA.
Jira (PUP-10925) Default timeout not respected for Windows services
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10925 Default timeout not respected for Windows services Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: This fix allows provider to be asked for default timeout value for syncing service properties when it has one instead of always defaulting to 10. This was causing issues on Windows when services were taking more than 10 seconds to change state or sync properties instead of waiting for 30 seconds as the provider was set to. 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.387947.1613664109000.131194.1631790600030%40Atlassian.JIRA.
Jira (FACT-3074) '--log-level none' throws exception
Title: Message Title Gerard Kok created an issue Facter / FACT-3074 '--log-level none' throws exception Issue Type: Bug Affects Versions: FACT 4.2.3 Assignee: Unassigned Components: Facter 4 Created: 2021/09/16 12:57 AM Environment: Verified on: macOS 11.6 Ubuntu 20.04 Priority: Normal Reporter: Gerard Kok facter --log-level none throws an exception, despite the help (facter --help) mentioning it as an option. The exception: $ facter --log-level none Traceback (most recent call last): 16: from /opt/puppetlabs/puppet/bin/facter:10:in `' 15: from
Jira (PDB-5257) Example code for PuppetDB query is not correct
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5257 Example code for PuppetDB query is not correct Change By: Bogdan Irimie Sprint: ghost-22.09.2021 Team: PuppetDB Ghost 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.414481.1630996799000.131123.1631777100328%40Atlassian.JIRA.
Jira (PDB-5257) Example code for PuppetDB query is not correct
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5257 Example code for PuppetDB query is not correct Change By: Bogdan Irimie Story Points: 1 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.414481.1630996799000.131124.1631777100376%40Atlassian.JIRA.
Jira (PDB-5257) Example code for PuppetDB query is not correct
Title: Message Title Bogdan Irimie assigned an issue to Sebastian Miclea PuppetDB / PDB-5257 Example code for PuppetDB query is not correct Change By: Bogdan Irimie Assignee: Bogdan Irimie Sebastian Miclea 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.414481.1630996799000.131122.1631777100267%40Atlassian.JIRA.
Jira (PDB-5257) Example code for PuppetDB query is not correct
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie PuppetDB / PDB-5257 Example code for PuppetDB query is not correct Change By: Bogdan Irimie Assignee: Bogdan Irimie 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.414481.1630996799000.131117.1631777040068%40Atlassian.JIRA.
Jira (PDB-5256) Puppet Query should have proper error message when it is failed
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5256 Puppet Query should have proper error message when it is failed Change By: Bogdan Irimie Story Points: 2 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.414480.1630996076000.131116.1631777040047%40Atlassian.JIRA.
Jira (PDB-5256) Puppet Query should have proper error message when it is failed
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5256 Puppet Query should have proper error message when it is failed Change By: Bogdan Irimie Sprint: ghost-22.09.2021 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.414480.1630996076000.131115.1631776920035%40Atlassian.JIRA.
Jira (PDB-5256) Puppet Query should have proper error message when it is failed
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5256 Puppet Query should have proper error message when it is failed Change By: Bogdan Irimie Team: PuppetDB Ghost 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.414480.1630996076000.131114.1631776860031%40Atlassian.JIRA.
Jira (PDB-4985) Querying for trusted on the inventory endpoint doesn't hit the index
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-4985 Querying for trusted on the inventory endpoint doesn't hit the index Change By: Bogdan Irimie Sprint: ghost-11.08.2021 , ghost-22.09.2021 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.380554.1607543476000.131113.1631776800031%40Atlassian.JIRA.
