Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publication of Galaxy Release v 16.04 #41

Open
3 of 36 tasks
jmchilton opened this issue Jan 28, 2016 · 0 comments
Open
3 of 36 tasks

Publication of Galaxy Release v 16.04 #41

jmchilton opened this issue Jan 28, 2016 · 0 comments

Comments

@jmchilton
Copy link
Owner

  • Prep
    • Create this release issue make release-issue RELEASE_CURR=16.04.
    • Set freeze date (2016-04-04).
  • Branch Release (on or around 2016-04-04)
    • Ensure all blocking milestone PRs have been merged, delayed, or closed.

      make release-check-blocking-prs RELEASE_CURR=16.04
      
    • Merge the latest release into dev.

      git fetch upstream && git checkout dev && git merge --ff-only upstream dev && git merge upstream release_16.01
      
    • Create and push release branch:

      make release-create-rc RELEASE_CURR=16.04 RELEASE_NEXT=16.07
      
  • Deploy and Test Release
    • Deploy to test (2016-04-04 + 1 day).
    • Deploy to usegalaxy.org (2016-04-04 + 1 week).
  • Create Release Notes
    • Review merged PRs and ensure they all milestones attached. Link

    • Checkout release branch

      git checkout 16.04 -b 16.04_release_notes
      
    • Check for obvious missing metadata in release PRs

      make release-check-metadata RELEASE_CURR=16.04
      
    • Bootstrap the release notes

      make release-bootstrap-history RELEASE_CURR=16.04
      
    • Open newly created files and manually curate major topics and release notes.

    • Commit release notes.

      git add docs/; git commit -m "Release notes for 16.04"; git push upstream 16.04_release_notes
      
    • Open a pull request for new release note branch.

    • Merge release note pull request.

  • Do Release
    • Ensure all blocking milestone issues have been resolved.

      make release-check-blocking-issues RELEASE_CURR=16.04
      
    • Ensure all blocking milestone PRs have been merged or closed.

      make release-check-blocking-prs RELEASE_CURR=16.04
      
    • Do release (TODO: create a check a list for this...)

  • Announce Release
  • Prepare for next release
    • Ensure milestone 16.07 exists.
    • Create release issue for next version make release-issue RELEASE_CURR=16.07.
    • Close this issue.
jmchilton added a commit that referenced this issue Jan 28, 2016
Create new makefile targets for release management.

 - ``release-create-issue``: Automates creating a release checklist - #41)
   Check list contains actual tailored ``make`` commands and links (for PRs and issues).
 - ``release-check-metadata``: Checks milestone PRs for required metadata needed for generating bootstrapped release notes.
 ` ``release-bootstrap-history``: Bootstrap release notes from PRs and metadata.
 - ``release-check-blocking-prs``: Check for PRs blocking release, should happen before branching release and before tagging release.
 - ``release-check-blocking-issues``: Check for Issues blocking release, should happen before tagging release. (Only allowed issue is the release creation issue.)

The issue created with ``release-create-issue`` documents how and when to execute subsequent ``make`` targets (including the target to create the issue for the next release).

This PR contains a bunch of other enhancements to the bootstrap_history.py script to enable these targets and renames ``create_release_rc`` Makefile target so all release related targets start with the prefix ``release-``.
jmchilton added a commit that referenced this issue Jan 28, 2016
Create new makefile targets for release management.

 - ``release-create-issue``: Automates creating a release checklist - #41)
   Check list contains actual tailored ``make`` commands and links (for PRs and issues).
 - ``release-check-metadata``: Checks milestone PRs for required metadata needed for generating bootstrapped release notes.
 ` ``release-bootstrap-history``: Bootstrap release notes from PRs and metadata.
 - ``release-check-blocking-prs``: Check for PRs blocking release, should happen before branching release and before tagging release.
 - ``release-check-blocking-issues``: Check for Issues blocking release, should happen before tagging release. (Only allowed issue is the release creation issue.)

The issue created with ``release-create-issue`` documents how and when to execute subsequent ``make`` targets (including the target to create the issue for the next release).

This PR contains a bunch of other enhancements to the bootstrap_history.py script to enable these targets and renames ``create_release_rc`` Makefile target so all release related targets start with the prefix ``release-``.
jmchilton added a commit that referenced this issue Mar 16, 2016
Create new makefile targets for release management.

 - ``release-create-issue``: Automates creating a release checklist - #41)
   Check list contains actual tailored ``make`` commands and links (for PRs and issues).
 - ``release-check-metadata``: Checks milestone PRs for required metadata needed for generating bootstrapped release notes.
 ` ``release-bootstrap-history``: Bootstrap release notes from PRs and metadata.
 - ``release-check-blocking-prs``: Check for PRs blocking release, should happen before branching release and before tagging release.
 - ``release-check-blocking-issues``: Check for Issues blocking release, should happen before tagging release. (Only allowed issue is the release creation issue.)

The issue created with ``release-create-issue`` documents how and when to execute subsequent ``make`` targets (including the target to create the issue for the next release).

This PR contains a bunch of other enhancements to the bootstrap_history.py script to enable these targets and renames ``create_release_rc`` Makefile target so all release related targets start with the prefix ``release-``.

Conflicts:
	Makefile
jmchilton pushed a commit that referenced this issue Feb 7, 2019
jmchilton pushed a commit that referenced this issue Sep 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant