Task #7558
Release 0.4.0
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
History
#1
Updated by bmbouter about 1 year ago
- Checklist item deleted (
Create a pulp_ansible (Not Shared) Sprint/Milestone with the name of the release, e.g. 1.2.1) - Checklist item deleted (
Run the release script. More info at https://pulp.plan.io/projects/pulp/wiki/Release_script) - Checklist item deleted (
Use the query from the release script to assign the release issues to your milestone) - Checklist item deleted (
Make a PR with the commits that the release script made and get it merged) - Checklist item deleted (
Create a release at https://github.com/pulp/pulp_ansible/releases/new from the recent commit w/ "Release x.y.z") - Checklist item deleted (
Confirm that the release job finished successfully in Travis and that the release is on PyPI) - Checklist item deleted (
Announce the release on pulp-dev@redhat.com and pulp-list@redhat.com with a summary of all the changes) - Checklist item deleted (
Cherry pick the change log commit to master (e.g. `git cherry-pick -x abc1234`)) - Checklist item Create a pulp_ansible (Not Shared) Sprint/Milestone with the name of the release, e.g. 1.2.0 added
- Checklist item Check for any issues still at MODIFIED. Optimally, there should be no MODIFIED issues after a y-release added
- Checklist item Create the stable branch from your tag (e.g. 1.2.0 would be a 1.2 release branch) added
- Checklist item Update pulpcore_branch and pulpcore_pip_version_specifier on your new branch (not master!) added
- Checklist item Update the supported-releases.json file (eg https://github.com/pulp/pulp-ci/pull/696) added
- Checklist item Increment version in setup.py, pulp_file/\_\_init\_\_.py, and .bumpversion.cfg to the next z-release added
- Checklist item Update stable_branch in template_config.yml on master added
- Subject changed from Release 0.3.1 to Release 0.4.0
#2
Updated by bmbouter about 1 year ago
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
#3
Updated by bmbouter about 1 year ago
- Checklist item Create a pulp_ansible (Not Shared) Sprint/Milestone with the name of the release, e.g. 1.2.0 set to Done
- Checklist item Check for any issues still at MODIFIED. Optimally, there should be no MODIFIED issues after a y-release set to Done
#4
Updated by daviddavis about 1 year ago
- Checklist item deleted (
Create a pulp_ansible (Not Shared) Sprint/Milestone with the name of the release, e.g. 1.2.0) - Checklist item deleted (
Check for any issues still at MODIFIED. Optimally, there should be no MODIFIED issues after a y-release) - Checklist item deleted (
Create the stable branch from your tag (e.g. 1.2.0 would be a 1.2 release branch)) - Checklist item deleted (
Update pulpcore_branch and pulpcore_pip_version_specifier on your new branch (not master!)) - Checklist item deleted (
Update the supported-releases.json file (eg https://github.com/pulp/pulp-ci/pull/696)) - Checklist item deleted (
Increment version in setup.py, pulp_file/\_\_init\_\_.py, and .bumpversion.cfg to the next z-release) - Checklist item deleted (
Update stable_branch in template_config.yml on master)
#5
Updated by daviddavis about 1 year ago
- Checklist item Create a pulp_ansible (Not Shared) Sprint/Milestone with the name of the release, e.g. 1.2.0 added
- Checklist item Run the release script. More info at https://pulp.plan.io/projects/pulp/wiki/Release_script added
- Checklist item Use the query from the release script to assign the release issues to your milestone added
- Checklist item Make a PR with the commits that the release script made and get it merged added
- Checklist item Create a release at https://github.com/pulp/pulp_ansible/releases/new from the recent commit w/ "Release x.y.z" added
- Checklist item Confirm that the release job finished successfully in Travis and that the release is on PyPI added
- Checklist item Announce the release on pulp-dev@redhat.com and pulp-list@redhat.com with a summary of all the changes added
- Checklist item Check for any issues still at MODIFIED. Optimally, there should be no MODIFIED issues after a y-release added
- Checklist item Create the stable branch from your tag (e.g. 1.2.0 would be a 1.2 release branch) added
- Checklist item Update pulpcore_branch and pulpcore_pip_version_specifier on your new branch (not master!) added
- Checklist item Update the supported-releases.json file (eg https://github.com/pulp/pulp-ci/pull/696) added
- Checklist item Increment version in setup.py, pulp_file/\_\_init\_\_.py, and .bumpversion.cfg to the next z-release added
- Checklist item Update stable_branch in template_config.yml on master added
#6
Updated by bmbouter about 1 year ago
- Checklist item Use the query from the release script to assign the release issues to your milestone set to Done
#7
Updated by bmbouter about 1 year ago
- Checklist item Make a PR with the commits that the release script made and get it merged set to Done
#8
Updated by bmbouter about 1 year ago
- Checklist item Create a release at https://github.com/pulp/pulp_ansible/releases/new from the recent commit w/ "Release x.y.z" set to Done
#9
Updated by bmbouter about 1 year ago
- Checklist item Confirm that the release job finished successfully in Travis and that the release is on PyPI set to Done
#10
Updated by bmbouter about 1 year ago
- Checklist item Check for any issues still at MODIFIED. Optimally, there should be no MODIFIED issues after a y-release set to Done
- Checklist item Create the stable branch from your tag (e.g. 1.2.0 would be a 1.2 release branch) set to Done
#11
Updated by bmbouter about 1 year ago
- Checklist item Update the supported-releases.json file (eg https://github.com/pulp/pulp-ci/pull/696) set to Done
#12
Updated by fao89 about 1 year ago
- Status changed from ASSIGNED to CLOSED - COMPLETE
Please register to edit this issue
.