Task #8355
Release 1.6.0
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 92
Quarter:
Q1-2021
History
#1
Updated by ttereshc about 1 month ago
- Checklist item Create a pulp_file (Not Shared) Sprint/Milestone with the name of the release, e.g. 1.2.0 set to Done
- Checklist item Run the release script. More info at https://pulp.plan.io/projects/pulp/wiki/Release_script set to Done
- Checklist item Use the query from the release script to assign the release issues to your milestone set to Done
- Checklist item Make a PR with the commits that the release script made and get it merged set to Done
#2
Updated by ttereshc about 1 month ago
- Checklist item Create a release at https://github.com/pulp/pulp_file/releases/new from the recent commit labeled "Release x.y.z" set to Done
#3
Updated by ttereshc about 1 month ago
- Sprint/Milestone changed from 1.5.0 to 1.6.0
#4
Updated by ttereshc about 1 month ago
- Checklist item Create the stable branch from your tag (e.g. 1.2.0 would be a 1.2 release branch) set to Done
- Checklist item On the stable branch, update version in setup.py, pulp_file/\_\_init\_\_.py, and .bumpversion.cfg to next z-release set to Done
#5
Updated by ttereshc about 1 month ago
- Checklist item Confirm that the release job finished successfully in Travis and that the release is on PyPI set to Done
- Checklist item Announce the release on pulp-dev@redhat.com and pulp-list@redhat.com with a summary of all the changes set to Done
#6
Updated by ttereshc about 1 month ago
- Checklist item Update pulpcore_pip_version_specifier on your new stable branch (not master!) (eg "~=3.1.0") set to Done
- Checklist item Regenerate the travis files on the stable branch with plugin_template (`./plugin-template --travis pulp_file`) set to Done
- Checklist item Open a PR against the stable branch with the pulpcore_branch and pulpcore_pip_version_specifier changes set to Done
#7
Updated by ttereshc about 1 month ago
- Checklist item Check for any issues still at MODIFIED. Optimally, there should be no MODIFIED issues after a y-release set to Done
#8
Updated by ttereshc about 1 month ago
- Status changed from ASSIGNED to CLOSED - COMPLETE
Please register to edit this issue