Notes about the process surrounding the galaxy-importer package, which is a dependency of projects such as:
- Automation Hub galaxy_ng
- pulp-ansible
- Community Galaxy galaxy
- Issues are located at issues.redhat.com JIRA
- Add a changelog entry to
CHANGES/. Changelog filename should be the number of the JIRA issue, and the extension of.feature,.bugfix,.doc,.removal, or.misc- see towncrier for descriptions of each extension. Example:CHANGES/56.feature. File contents should be a one line description of the change. - At least one commit must include a reference to a Jira issue on a single line in the format of
Issue: AAH-1111 - If Pull Request is small enough not to need a Jira issue, at least one commit must include a single line with
No-Issue - Please run the tests in
Makefileor install the pre-commit hook inhooks/pre-commitand correct any failures prior to submitting a pull request.
- Prioritized list of tickets labeled
importer
Versioning (x.y.z) following https://semver.org/
- Advance the x-stream if breaking backwards-compatibility
- Advance the y-stream for new features
- Advance the z-stream for bugfixes / ci / minor changes
- Open PR with title
Release #.#.#- Update
galaxy_importer/__init__.pywith new version number- Be aware of
galaxy-importerversion range dependencies in pulp_ansible and galaxy_ng
- Be aware of
- Run
$ towncrierto updateCHANGES.rst
- Update
- Merge PR
- Check the master branch CI on the merged commit to ensure it is green
- Tag the commit
v<#.#.#>, and push the tag to upstream repo - Check the master branch CI on the merged and tagged commit, it will execute a new job to publish to pypi
- Latest
galaxy-importerrelease will get consumed intopulp-ansiblenightly builds - Automation Hub JIRA AAH issues may specify a
galaxy-importerchange and agalaxy_ngPR will include a new release ofgalaxy-importerfor testing by QE - Community Galaxy galaxy importer issues will include a
galaxyPR with new release ofgalaxy-importer, and get tagged for QE