Skip to content

Commit 1f34cca

Browse files
committed
Update issues URL
This commit updates the README's references to Jira to use GitHub issues instead. I have also updated references to Puppet versions in the README to more current versions.
1 parent 9ceca21 commit 1f34cca

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ See [LICENSE](https://github.com/puppetlabs/puppet/blob/main/LICENSE) file. Pupp
4646

4747
## Support
4848

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
5050
list](https://groups.google.com/forum/?fromgroups#!forum/puppet-users) is
5151
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/)
5252

@@ -58,9 +58,9 @@ Bug fixes and ongoing development will occur in minor releases for the current
5858
major version. Security fixes will be backported to a previous major version on
5959
a best-effort basis, until the previous major version is no longer maintained.
6060

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.
6464

6565
Long-term support, including security patches and bug fixes, is available for
6666
commercial customers. Please see the following page for more details:

0 commit comments

Comments
 (0)