Description
-
Prep
-
Create this release issuemake release-issue RELEASE_CURR=18.05
. -
Set freeze date (2018-05-07).
-
-
Branch Release (on or around 2018-04-23)
-
Ensure all blocking milestone PRs have been merged, delayed, or closed.
make release-check-blocking-prs RELEASE_CURR=18.05
-
Merge the latest release into dev and push upstream.
make release-merge-stable-to-next RELEASE_PREVIOUS=release_18.01 make release-push-dev
-
Create and push release branch:
make release-create-rc RELEASE_CURR=18.05 RELEASE_NEXT=18.09
-
Open PRs from your fork of branch
version-18.05
to upstreamrelease_18.05
and ofversion-18.09.dev
todev
. -
Update
next_milestone
in P4's configuration to18.09
so it properly tags new PRs. -
Set the
release_18.05
branch in GitHub settings as protected.
-
-
Deploy and Test Release
- Update test.galaxyproject.org to ensure it is running a dev at or past branch point (2018-04-23).
- Update testtoolshed.g2.bx.psu.edu to ensure it is running a dev at or past branch point (2018-04-23).
- Deploy to usegalaxy.org (2018-04-30).
- Deploy to toolshed.g2.bx.psu.edu (2018-05-07).
- Update BioBlend CI testing to include a
release_18.05
target: add- TOX_ENV=py27 GALAXY_VERSION=release_18.05
to theenv
list in.travis.yml
.
-
Create Release Notes (2018-04-30)
-
Review merged PRs and ensure they all have a milestones attached. Link
-
Checkout release branch
git checkout release_18.05 -b 18.05_release_notes
-
Check for obvious missing metadata in release PRs
make release-check-metadata RELEASE_CURR=18.05
-
Bootstrap the release notes
make release-bootstrap-history RELEASE_CURR=18.05
-
Open newly created files and manually curate major topics and release notes.
-
Commit release notes.
git add docs/; git commit -m "Release notes for 18.05"; git push upstream 18.05_release_notes
-
Open a pull request for new release note branch.
-
Merge release note pull request.
-
-
Do Release (2018-05-07)
-
Ensure all blocking milestone issues have been resolved.
make release-check-blocking-issues RELEASE_CURR=18.05
-
Ensure all blocking milestone PRs have been merged or closed.
make release-check-blocking-prs RELEASE_CURR=18.05
-
Ensure previous release is merged into current. Github branch comparison
-
Create and push release tag:
make release-create RELEASE_CURR=18.05
-
Add the branch
*/release_{version}
to Jenkins documentation build configuration matrix. -
Trigger the documentation build.
-
-
Do Docker Release
- Change the dev branch of the Galaxy Docker container to 18.09
- Merge dev into master
-
Ensure Tool Tests use Latest Release
- Update GALAXY_RELEASE in https://github.com/galaxyproject/tools-iuc/blob/master/.travis.yml#L6
- Update GALAXY_RELEASE in https://github.com/galaxyproject/tools-devteam/blob/master/.travis.yml#L6
-
Announce Release
- Verify release included in https://docs.galaxyproject.org/en/master/releases/index.html
- Review announcement in https://github.com/galaxyproject/galaxy/blob/dev/doc/source/releases/18.05_announce.rst
- Stage annoucement content (Hub, Biostars, Bit.ly link) on annouce date to capture date tags. Note: all final content does not need to be completed to do this.
- Create hub highlights and post to http://galaxyproject.org News (w/ RSS) and NewsBriefs. An Example.
- Tweet docs news highlights via bit.ly link to https://twitter.com/galaxyproject/. An Example.
- Post highlights type News to Galaxy Biostars https://biostar.usegalaxy.org. An Example.
- Email highlights to galaxy-dev and galaxy-announce @lists.galaxyproject.org. An Example
- Adjust http://getgalaxy.org text and links to match current master branch by opening a PR for https://github.com/galaxyproject/galaxy-hub/
-
Prepare for next release
- Ensure milestone
18.09
exists. - Create release issue for next version
make release-issue RELEASE_CURR=18.09
. - Schedule committer meeting to discuss re-alignment of priorities.
- Close this issue.
- Ensure milestone