Project

Profile

Help

Task #7463

3.7.0 Release

Added by bmbouter about 2 months ago. Updated 23 days ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Timeline

Sept 22, 2020

Go / No-Go

On #pulp-meeting on Tuesday Sept 15th, 12pm - 12:30pm EDT. https://everytimezone.com/s/68f4535a

Personnel

bmbouter to release pulpcore, pulp_file, and pulp_installer

Milestone link

https://pulp.plan.io/versions/126


Checklist

History

#1 Updated by bmbouter about 2 months ago

  • Checklist item [Tag plugin_template](https://github.com/pulp/plugin_template#tagging-plugin_template) added
  • Checklist item Create a pulpcore (Not Shared) Sprint/Milestone with the name of the release, e.g. 3.0.1 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 Tag the commit that the release script indicated. This is the "Release x.y.z" commit. added
  • Checklist item Push your tag to github (e.g. `git push upstream 3.0.1`) added
  • Checklist item Go to https://github.com/pulp/pulpcore/releases/new and create a new release from the tag 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 If a z-stream release, cherry pick the change log commit to master (e.g. `git cherry-pick -x abc1234`) added
  • Checklist item If a y-release, check for any issues still at MODIFIED. Optimally, there should be no MODIFIED issues added
  • Checklist item If a y-release, create the stable branch from your tag (e.g. 3.5.0 would be a 3.5 release branch) added
  • Checklist item If a y-release, update pulpcore_branch and pulpcore_pip_version_specifier on your new branch (not master!) added
  • Checklist item If a y-release, update the supported-releases.json file (eg https://github.com/pulp/pulp-ci/pull/696) added
  • Checklist item If a y-release, increment version in setup.py, pulpcore/\_\_init\_\_.py, and .bumpversion.cfg to the next z-release added
  • Checklist item If a y-release, update stable_branch in template_config.yml on master added

#2 Updated by bmbouter about 2 months ago

  • Subject changed from Release 3.7.0 to 3.7.0 Release
  • Description updated (diff)

#3 Updated by daviddavis about 2 months ago

  • Checklist item deleted (If a z-stream release, cherry pick the change log commit to master (e.g. `git cherry-pick -x abc1234`))

#4 Updated by daviddavis about 2 months ago

  • Sprint/Milestone set to 3.7.0

#5 Updated by bmbouter about 2 months ago

  • Checklist item deleted ([Tag plugin_template](https://github.com/pulp/plugin_template#tagging-plugin_template))
  • Checklist item deleted (Create a pulpcore (Not Shared) Sprint/Milestone with the name of the release, e.g. 3.0.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 (Tag the commit that the release script indicated. This is the "Release x.y.z" commit.)
  • Checklist item deleted (Push your tag to github (e.g. `git push upstream 3.0.1`))
  • Checklist item deleted (Go to https://github.com/pulp/pulpcore/releases/new and create a new release from the tag)
  • 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 (If a y-release, check for any issues still at MODIFIED. Optimally, there should be no MODIFIED issues)
  • Checklist item deleted (If a y-release, create the stable branch from your tag (e.g. 3.5.0 would be a 3.5 release branch))
  • Checklist item deleted (If a y-release, update pulpcore_branch and pulpcore_pip_version_specifier on your new branch (not master!))
  • Checklist item deleted (If a y-release, update the supported-releases.json file (eg https://github.com/pulp/pulp-ci/pull/696))
  • Checklist item deleted (If a y-release, increment version in setup.py, pulpcore/\_\_init\_\_.py, and .bumpversion.cfg to the next z-release)
  • Checklist item deleted (If a y-release, update stable_branch in template_config.yml on master)
  • 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. 3.5.0 would be a 3.5 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, pulpcore/\_\_init\_\_.py, and .bumpversion.cfg to the next z-release added
  • Checklist item Update stable_branch in template_config.yml on master added

reapply the revised checklist

#6 Updated by daviddavis about 2 months ago

  • 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. 3.5.0 would be a 3.5 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, pulpcore/\_\_init\_\_.py, and .bumpversion.cfg to the next z-release)
  • Checklist item deleted (Update stable_branch in template_config.yml on master)

#7 Updated by daviddavis about 2 months ago

  • Checklist item [Tag plugin_template](https://github.com/pulp/plugin_template#tagging-plugin_template) added
  • Checklist item Create a pulpcore (Not Shared) Sprint/Milestone with the name of the release, e.g. 3.0.1 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 Tag the commit that the release script indicated. This is the "Release x.y.z" commit. added
  • Checklist item Push your tag to github (e.g. `git push upstream 3.0.1`) added
  • Checklist item Go to https://github.com/pulp/pulpcore/releases/new and create a new release from the tag 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. 3.5.0 would be a 3.5 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, pulpcore/\_\_init\_\_.py, and .bumpversion.cfg to the next z-release added
  • Checklist item Update stable_branch in template_config.yml on master added

#8 Updated by daviddavis about 2 months ago

  • Sprint/Milestone deleted (3.7.0)

#9 Updated by bmbouter about 1 month ago

  • Checklist item [Tag plugin_template](https://github.com/pulp/plugin_template#tagging-plugin_template) set to Done
  • Checklist item Create a pulpcore (Not Shared) Sprint/Milestone with the name of the release, e.g. 3.0.1 set to Done

#10 Updated by bmbouter about 1 month ago

  • 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

#11 Updated by bmbouter about 1 month ago

  • Checklist item Tag the commit that the release script indicated. This is the "Release x.y.z" commit. set to Done
  • Checklist item Push your tag to github (e.g. `git push upstream 3.0.1`) set to Done
  • Checklist item Go to https://github.com/pulp/pulpcore/releases/new and create a new release from the tag set to Done

#12 Updated by bmbouter 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

#13 Updated by bmbouter 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
  • Checklist item Create the stable branch from your tag (e.g. 3.5.0 would be a 3.5 release branch) set to Done

#14 Updated by bmbouter about 1 month ago

  • Checklist item Update the supported-releases.json file (eg https://github.com/pulp/pulp-ci/pull/696) set to Done

#15 Updated by bmbouter about 1 month ago

  • 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

#16 Updated by daviddavis 29 days ago

  • Checklist item Update stable_branch in template_config.yml on master set to Done

#17 Updated by bmbouter 23 days ago

  • Checklist item Increment version in setup.py, pulpcore/\_\_init\_\_.py, and .bumpversion.cfg to the next z-release set to Done

#18 Updated by bmbouter 23 days ago

  • Checklist item Update pulpcore_branch and pulpcore_pip_version_specifier on your new branch (not master!) set to Done

#19 Updated by bmbouter 23 days ago

  • Status changed from NEW to CLOSED - COMPLETE

Please register to edit this issue

Also available in: Atom PDF