Migrate issue management to Jira

This commit is contained in:
Jake Spain 2023-04-20 08:51:12 -04:00
parent 1d4d931a10
commit 2f0e817b7c
No known key found for this signature in database
GPG key ID: BC1C4DA0A085E113

View file

@ -4,6 +4,7 @@
- [Usage](#usage) - [Usage](#usage)
- [Custom VM Config Attribute](#custom-vm-config-attribute) - [Custom VM Config Attribute](#custom-vm-config-attribute)
- [Update the Gemfile Lock](#update-the-gemfile-lock) - [Update the Gemfile Lock](#update-the-gemfile-lock)
- [Submitting Issues](#submitting-issues)
- [Releasing](#releasing) - [Releasing](#releasing)
- [License](#license) - [License](#license)
@ -30,6 +31,10 @@ To update the `Gemfile.lock` run `./update-gemfile-lock`.
Verify, and update if needed, that the docker tag in the script and GitHub action workflows matches what is used in the [vmpooler-deployment Dockerfile](https://github.com/puppetlabs/vmpooler-deployment/blob/main/docker/Dockerfile). Verify, and update if needed, that the docker tag in the script and GitHub action workflows matches what is used in the [vmpooler-deployment Dockerfile](https://github.com/puppetlabs/vmpooler-deployment/blob/main/docker/Dockerfile).
## Submitting Issues
Please file any issues or requests in Jira at <https://puppet.atlassian.net/jira/software/c/projects/POOLER/issues> where project development is tracked across all VMPooler related components.
## Releasing ## Releasing
Follow these steps to publish a new GitHub release, and build and push the gem to <https://rubygems.org>. Follow these steps to publish a new GitHub release, and build and push the gem to <https://rubygems.org>.