Pulp

Added by ipanova@redhat.com 14 days ago. Updated about 17 hours ago.

Checklist

• Tag plugin_template
• Make sure that CI is up to date, bring changes from the plugin template if there are any added
• Create a pulpcore (Not Shared) Sprint/Milestone with the name of the release, e.g. 3.1.0
• Run the release script. More info at https://pulp.plan.io/projects/pulp/wiki/Release_script
• Use the query from the release script to assign the release issues to your milestone
• Make a PR with the commits that the release script made and get it merged
• Create a release at https://github.com/pulp/pulpcore/releases/new from the recent commit labeled "Release x.y.z"
• Confirm that the release job finished successfully in GHA and that the release is on PyPI
• Check for any issues still at MODIFIED. Optimally, there should be no MODIFIED issues after a y-release
• Update the supported-releases.json file in pulp-ci (eg https://github.com/pulp/pulp-ci/pull/696)
• Create the stable branch from your tag (e.g. 3.5.0 would be a 3.5 release branch)
• On this branch, update version in setup.py, pulpcore/__init__.py, and .bumpversion.cfg to the next z-release
• Release pulp_installer
• Release a new pulp container image tag
• Announce the release on pulp-dev@redhat.com and pulp-list@redhat.com with a summary of all the changes