Jira (PUP-10159) Can't differentiate between cert and request on Puppet Server
Title: Message Title Maggie Dreyer assigned an issue to Unassigned Puppet / PUP-10159 Can't differentiate between cert and request on Puppet Server Change By: Maggie Dreyer Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335692.1574091306000.7704.1576800840747%40Atlassian.JIRA.
Jira (PDB-4606) Partition the reports table
Title: Message Title Eric Thompson commented on PDB-4606 Re: Partition the reports table FWIW, i agree with Rob here. It feels like this can be handled with documentation and with the expert guidance our CS and SEs provide to our larger customers. If we have issues later, perhaps we can talk about a setting or providing truncation automation. This change is critical to Plans in PE supporting Plan reports in PDB. I wouldn't want to hold-up that critical product priority. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340126.1576694351000.7595.1576797900335%40Atlassian.JIRA.
Jira (PDB-4606) Partition the reports table
Title: Message Title Robert Roland commented on PDB-4606 Re: Partition the reports table I would prefer this to be handled entirely via documentation, where we document how to truncate this table, maybe even provide a script that assists them with it. Adding a setting adds additional complexity to PuppetDB (the setting itself, validation, code to use it, unit tests, integration tests) that may not be extra maintenance in the future. I don't know of any other migrations where we have done this. This isn't without precedent - there are already scripted truncation of tables via cron running at customer sites. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340126.1576694351000.7521.1576797000267%40Atlassian.JIRA.
Jira (PUP-10159) Can't differentiate between cert and request on Puppet Server
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10159 Can't differentiate between cert and request on Puppet Server Change By: Maggie Dreyer Team: Froyo Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335692.1574091306000.7341.1576794360955%40Atlassian.JIRA.
Jira (PUP-10159) Can't differentiate between cert and request on Puppet Server
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10159 Can't differentiate between cert and request on Puppet Server Change By: Maggie Dreyer Team: Froyo Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335692.1574091306000.7344.1576794361087%40Atlassian.JIRA.
Jira (PDB-4606) Partition the reports table
Title: Message Title Nick Walker commented on PDB-4606 Re: Partition the reports table Could we add a configuration setting that truncates the reports table before performing this migration? The reason I ask is because we suggest to many users that they truncate the reports table before large migrations with the reports table ( or postgresql upgrades) and performing the truncation requiring dropping an FK and recreating it unless you want to delete the entire contents of your database. If it seems reasonable then adding documentation like "add this setting to puppetdb before upgrading" is a lot more palatable than run these SQL commands to remove all reports before the long migration. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340126.1576694351000.7294.1576791420175%40Atlassian.JIRA.
Jira (PDB-4618) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.7.3)
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4618 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.7.3) Issue Type: Task Assignee: Austin Blatt Created: 2019/12/19 11:25 AM Due Date: 2020/01/07 Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PDB-4617) Merge-up, branch, and create pipelines (PuppetDB 6.7.3)
Title: Message Title
Sara Meisburger created an issue
PuppetDB / PDB-4617
Merge-up, branch, and create pipelines (PuppetDB 6.7.3)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2019/12/19 11:25 AM
Due Date:
2020/01/07
Priority:
Normal
Reporter:
Sara Meisburger
(Initial planned release date: 2020-01-14) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Merge 5.2.x -> 6.3.x
Merge
Jira (PDB-4619) Bump versions, push directly, and tag (PuppetDB 6.7.3)
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4619 Bump versions, push directly, and tag (PuppetDB 6.7.3) Issue Type: Task Assignee: Austin Blatt Created: 2019/12/19 11:25 AM Due Date: 2020/01/10 Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Disable automatic promotions: If this release will be released in a PE release, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. Go into the '#release-new-new' Slack channel to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in
Jira (PDB-4621) Update winston (PuppetDB 6.7.3)
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4621 Update winston (PuppetDB 6.7.3) Issue Type: Task Assignee: Austin Blatt Created: 2019/12/19 11:25 AM Due Date: 2020/01/15 Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4620) Check builds, promote to PE (PuppetDB 6.7.3)
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4620 Check builds, promote to PE (PuppetDB 6.7.3) Issue Type: Task Assignee: Austin Blatt Created: 2019/12/19 11:25 AM Due Date: 2020/01/10 Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PUP-10203) Prepare release announcement (Puppet Platform 6.12.0)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10203 Prepare release announcement (Puppet Platform 6.12.0) Issue Type: Task Assignee: Jed Gresham Created: 2019/12/19 11:24 AM Due Date: 2020/01/13 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-10207) Update Confluence and JIRA based on release (Puppet Platform 6.12.0)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10207 Update Confluence and JIRA based on release (Puppet Platform 6.12.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:24 AM Due Date: 2020/01/15 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update
Jira (PUP-10204) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.12.0)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10204 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.12.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:24 AM Due Date: 2020/01/13 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in #proj-puppet-releases Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-10201) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.12.0)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10201 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.12.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:24 AM Due Date: 2020/01/08 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in Slack) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-10205) Publish documentation and updates and release notes (Puppet Platform 6.12.0)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10205 Publish documentation and updates and release notes (Puppet Platform 6.12.0) Issue Type: Task Assignee: Jean Bond Created: 2019/12/19 11:24 AM Due Date: 2020/01/14 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-10208) Communicate scope and timeline of next release (Puppet Platform 6.12.0)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10208 Communicate scope and timeline of next release (Puppet Platform 6.12.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:24 AM Due Date: 2020/01/15 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-10199) Puppet Platform 6.12.0 Release - 2020-01-14
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10199 Puppet Platform 6.12.0 Release - 2020-01-14 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/12/19 11:24 AM Due Date: 2020/01/14 Priority: Normal Reporter: Sara Meisburger Puppet Platform 6.12.0 Release - 2020-01-14 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10206) Send release announcement (Puppet Platform 6.12.0)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10206 Send release announcement (Puppet Platform 6.12.0) Issue Type: Task Assignee: Eric Griswold Created: 2019/12/19 11:24 AM Due Date: 2020/01/14 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.12.0 is now available".
Jira (PUP-10200) Prepare JIRA and Confluence for release (Puppet Platform 6.12.0)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10200 Prepare JIRA and Confluence for release (Puppet Platform 6.12.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:24 AM Due Date: 2020/01/08 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.12.0 and puppet-agent 6.12.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform
Jira (PUP-10202) Prepare documentation updates and release notes (Puppet Platform 6.12.0)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10202 Prepare documentation updates and release notes (Puppet Platform 6.12.0) Issue Type: Task Assignee: Jean Bond Created: 2019/12/19 11:24 AM Due Date: 2020/01/10 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Add Comment
Jira (PDB-4616) Update winston (PuppetDB 6.3.6)
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4616 Update winston (PuppetDB 6.3.6) Issue Type: Task Assignee: Austin Blatt Created: 2019/12/19 11:22 AM Due Date: 2020/01/15 Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4615) Check builds, promote to PE (PuppetDB 6.3.6)
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4615 Check builds, promote to PE (PuppetDB 6.3.6) Issue Type: Task Assignee: Austin Blatt Created: 2019/12/19 11:22 AM Due Date: 2020/01/10 Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4614) Bump versions, push directly, and tag (PuppetDB 6.3.6)
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4614 Bump versions, push directly, and tag (PuppetDB 6.3.6) Issue Type: Task Assignee: Austin Blatt Created: 2019/12/19 11:22 AM Due Date: 2020/01/10 Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Disable automatic promotions: If this release will be released in a PE release, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. Go into the '#release-new-new' Slack channel to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in
Jira (PDB-4612) Merge-up, branch, and create pipelines (PuppetDB 6.3.6)
Title: Message Title
Sara Meisburger created an issue
PuppetDB / PDB-4612
Merge-up, branch, and create pipelines (PuppetDB 6.3.6)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2019/12/19 11:22 AM
Due Date:
2020/01/07
Priority:
Normal
Reporter:
Sara Meisburger
(Initial planned release date: 2020-01-14) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Merge 5.2.x -> 6.3.x
Merge
Jira (PDB-4613) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.6)
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4613 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.6) Issue Type: Task Assignee: Austin Blatt Created: 2019/12/19 11:22 AM Due Date: 2020/01/07 Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PUP-10194) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.5)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10194 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.5) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:21 AM Due Date: 2020/01/13 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in #proj-puppet-releases Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-10198) Communicate scope and timeline of next release (Puppet Platform 6.4.5)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10198 Communicate scope and timeline of next release (Puppet Platform 6.4.5) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:21 AM Due Date: 2020/01/15 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-10195) Publish documentation and updates and release notes (Puppet Platform 6.4.5)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10195 Publish documentation and updates and release notes (Puppet Platform 6.4.5) Issue Type: Task Assignee: Jean Bond Created: 2019/12/19 11:21 AM Due Date: 2020/01/14 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-10190) Prepare JIRA and Confluence for release (Puppet Platform 6.4.5)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10190 Prepare JIRA and Confluence for release (Puppet Platform 6.4.5) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:21 AM Due Date: 2020/01/08 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.4.5 and puppet-agent 6.4.5 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PUP-10191) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.5)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10191 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.5) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:21 AM Due Date: 2020/01/08 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in Slack) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-10197) Update Confluence and JIRA based on release (Puppet Platform 6.4.5)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10197 Update Confluence and JIRA based on release (Puppet Platform 6.4.5) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:21 AM Due Date: 2020/01/15 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update
Jira (PUP-10196) Send release announcement (Puppet Platform 6.4.5)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10196 Send release announcement (Puppet Platform 6.4.5) Issue Type: Task Assignee: Eric Griswold Created: 2019/12/19 11:21 AM Due Date: 2020/01/14 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.4.5 is now available".
Jira (PUP-10192) Prepare documentation updates and release notes (Puppet Platform 6.4.5)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10192 Prepare documentation updates and release notes (Puppet Platform 6.4.5) Issue Type: Task Assignee: Jean Bond Created: 2019/12/19 11:21 AM Due Date: 2020/01/10 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Add Comment
Jira (PUP-10193) Prepare release announcement (Puppet Platform 6.4.5)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10193 Prepare release announcement (Puppet Platform 6.4.5) Issue Type: Task Assignee: Jed Gresham Created: 2019/12/19 11:21 AM Due Date: 2020/01/13 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-10189) Puppet Platform 6.4.5 Release - 2020-01-14
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10189 Puppet Platform 6.4.5 Release - 2020-01-14 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/12/19 11:21 AM Due Date: 2020/01/14 Priority: Normal Reporter: Sara Meisburger Puppet Platform 6.4.5 Release - 2020-01-14 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4607) Merge-up, branch, and create pipelines (PuppetDB 5.2.11)
Title: Message Title
Sara Meisburger created an issue
PuppetDB / PDB-4607
Merge-up, branch, and create pipelines (PuppetDB 5.2.11)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2019/12/19 11:19 AM
Due Date:
2020/01/07
Priority:
Normal
Reporter:
Sara Meisburger
(Initial planned release date: 2020-01-14) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Merge 5.2.x -> 6.3.x
Merge
Jira (PDB-4608) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.11)
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4608 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.11) Issue Type: Task Assignee: Austin Blatt Created: 2019/12/19 11:19 AM Due Date: 2020/01/07 Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PDB-4610) Check builds, promote to PE (PuppetDB 5.2.11)
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4610 Check builds, promote to PE (PuppetDB 5.2.11) Issue Type: Task Assignee: Austin Blatt Created: 2019/12/19 11:19 AM Due Date: 2020/01/10 Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4611) Update winston (PuppetDB 5.2.11)
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4611 Update winston (PuppetDB 5.2.11) Issue Type: Task Assignee: Austin Blatt Created: 2019/12/19 11:19 AM Due Date: 2020/01/15 Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4609) Bump versions, push directly, and tag (PuppetDB 5.2.11)
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4609 Bump versions, push directly, and tag (PuppetDB 5.2.11) Issue Type: Task Assignee: Austin Blatt Created: 2019/12/19 11:19 AM Due Date: 2020/01/10 Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Disable automatic promotions: If this release will be released in a PE release, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. Go into the '#release-new-new' Slack channel to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in
Jira (PUP-10180) Prepare JIRA and Confluence for release (Puppet Platform 5.5.18)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10180 Prepare JIRA and Confluence for release (Puppet Platform 5.5.18) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:18 AM Due Date: 2020/01/08 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 5.5.18 and puppet-agent 5.5.18 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform
Jira (PUP-10185) Publish documentation and updates and release notes (Puppet Platform 5.5.18)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10185 Publish documentation and updates and release notes (Puppet Platform 5.5.18) Issue Type: Task Assignee: Jean Bond Created: 2019/12/19 11:18 AM Due Date: 2020/01/14 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-10186) Send release announcement (Puppet Platform 5.5.18)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10186 Send release announcement (Puppet Platform 5.5.18) Issue Type: Task Assignee: Eric Griswold Created: 2019/12/19 11:18 AM Due Date: 2020/01/14 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 5.5.18 is now available".
Jira (PUP-10183) Prepare release announcement (Puppet Platform 5.5.18)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10183 Prepare release announcement (Puppet Platform 5.5.18) Issue Type: Task Assignee: Jed Gresham Created: 2019/12/19 11:18 AM Due Date: 2020/01/13 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-10184) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.18)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10184 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.18) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:18 AM Due Date: 2020/01/13 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in #proj-puppet-releases Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-10179) Puppet Platform 5.5.18 Release - 2020-01-14
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10179 Puppet Platform 5.5.18 Release - 2020-01-14 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/12/19 11:18 AM Due Date: 2020/01/14 Priority: Normal Reporter: Sara Meisburger Puppet Platform 5.5.18 Release - 2020-01-14 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10182) Prepare documentation updates and release notes (Puppet Platform 5.5.18)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10182 Prepare documentation updates and release notes (Puppet Platform 5.5.18) Issue Type: Task Assignee: Jean Bond Created: 2019/12/19 11:18 AM Due Date: 2020/01/10 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Add Comment
Jira (PUP-10181) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.18)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10181 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.18) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:18 AM Due Date: 2020/01/08 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in Slack) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-10188) Communicate scope and timeline of next release (Puppet Platform 5.5.18)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10188 Communicate scope and timeline of next release (Puppet Platform 5.5.18) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:18 AM Due Date: 2020/01/15 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-10187) Update Confluence and JIRA based on release (Puppet Platform 5.5.18)
Title: Message Title Sara Meisburger created an issue Puppet / PUP-10187 Update Confluence and JIRA based on release (Puppet Platform 5.5.18) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/12/19 11:18 AM Due Date: 2020/01/15 Labels: release Priority: Normal Reporter: Sara Meisburger (Initial planned release date: 2020-01-14) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update
Jira (PUP-10160) Puppet should not load types and providers during environment convergence
Title: Message Title Melissa Stone commented on PUP-10160 Re: Puppet should not load types and providers during environment convergence passed ci as a part of puppet-agent 5.5.17.154.g840d3bb0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.337880.157548855.6415.1576778340127%40Atlassian.JIRA.
Jira (FACT-2259) Implement mechanism to block legacy facts
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2259 Implement mechanism to block legacy facts Issue Type: New Feature Assignee: Unassigned Created: 2019/12/19 4:57 AM Priority: Normal Reporter: Oana Tanasoiu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2001) Prototype 4 should include OS detection and output format similar to the C++ facter
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2001 Prototype 4 should include OS detection and output format similar to the C++ facter Change By: Bogdan Irimie Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322385.156692812.6139.1576760160171%40Atlassian.JIRA.
Jira (FACT-2202) filesystems fact for OSX
Title: Message Title Gheorghe Campean assigned an issue to Gheorghe Campean Facter / FACT-2202 filesystems fact for OSX Change By: Gheorghe Campean Assignee: Gheorghe Campean Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338907.1576053099000.6134.1576759620216%40Atlassian.JIRA.
Jira (FACT-2213) processors fact for OSX
Title: Message Title George Mrejea assigned an issue to George Mrejea Facter / FACT-2213 processors fact for OSX Change By: George Mrejea Assignee: George Mrejea Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338919.1576054005000.6119.1576755960131%40Atlassian.JIRA.
Jira (FACT-2215) system_profiler fact for OSX
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-2215 system_profiler fact for OSX Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338921.157605405.6012.1576742820172%40Atlassian.JIRA.
