You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ See [LICENSE](https://github.com/puppetlabs/puppet/blob/main/LICENSE) file. Pupp
46
46
47
47
## Support
48
48
49
-
Please log tickets and issues at our [JIRA tracker](https://tickets.puppetlabs.com). A [mailing
49
+
Please log issues in this project's [GitHub Issues](https://github.com/puppetlabs/puppet/issues). A [mailing
50
50
list](https://groups.google.com/forum/?fromgroups#!forum/puppet-users) is
51
51
available for asking questions and getting help from others, or if you prefer chat, we also have a [Puppet Community slack.](https://puppetcommunity.slack.com/)
52
52
@@ -58,9 +58,9 @@ Bug fixes and ongoing development will occur in minor releases for the current
58
58
major version. Security fixes will be backported to a previous major version on
59
59
a best-effort basis, until the previous major version is no longer maintained.
60
60
61
-
For example: If a security vulnerability is discovered in Puppet 6.1.1, we
62
-
would fix it in the 6 series, most likely as 6.1.2. Maintainers would then make
63
-
a best effort to backport that fix onto the latest Puppet 5 release.
61
+
For example: If a security vulnerability is discovered in Puppet 8.1.1, we
62
+
would fix it in the 8 series, most likely as 8.1.2. Maintainers would then make
63
+
a best effort to backport that fix onto the latest Puppet 7 release.
64
64
65
65
Long-term support, including security patches and bug fixes, is available for
66
66
commercial customers. Please see the following page for more details:
0 commit comments