Publication of Galaxy Release v 23.1

[dannon]

• [X] Prep

  • [X] Create this release issue make release-issue.
  • [X] Set freeze date (2023-06-05).

• [ ] Branch Release (on or around 2023-06-05)

  • [ ] Ensure all blocking milestone PRs have been merged, delayed, or closed.

    make release-check-blocking-prs

  • [ ] Add latest database revision identifier (for release_23.1 and 23.1) to REVISION_TAGS in galaxy/model/migrations/dbscript.py.

  • [ ] Merge the latest release into dev and push upstream.

    make release-merge-stable-to-next RELEASE_PREVIOUS=release_23.0 make release-push-dev

  • [ ] Create and push release branch:

    make release-create-rc

  • [ ] Create dev packages:

    cd packages && DEV_RELEASE=1 ./build_packages.sh

  • [ ] Review created packages (HISTORY.rst correct, setup.cfg correct, correct version in filename)

  • [ ] Upload galaxy-util & galaxy-tool-util dev packages to pypi

  • [ ] Open PR against planemo with a pin to the dev packages

  • [ ] Open PRs from your fork of branch version-23.1 to upstream release_23.1 and of version-23.2.dev to dev.

  • [ ] Update MILESTONE_NUMBER in the maintenance bot to 23.2 so it properly tags new PRs.

• [ ] Issue Review Timeline Notes

  • [ ] Ensure any security fixes will be ready prior to 2023-06-05 + 1 week, to allow time for notification prior to release.
  • [ ] Ensure ownership of outstanding bugfixes and track progress during freeze.

• [ ] Deploy and Test Release

  • [ ] Update test.galaxyproject.org to ensure it is running a dev at or past branch point (2023-06-05 + 1 day).
  • [ ] Update testtoolshed.g2.bx.psu.edu to ensure it is running a dev at or past branch point (2023-06-05 + 1 day).
  • [ ] Deploy to usegalaxy.org (2023-06-05 + 1 week).
  • [ ] Deploy to toolshed.g2.bx.psu.edu (2023-06-05 + 1 week).
  • [ ] Update BioBlend CI testing to include a release_23.1 target: add - release_23.1 to the galaxy_version list in .github/workflows/test.yaml .
  • [ ] Update GALAXY_RELEASE in IUC and devteam github workflows
    • [ ] https://github.com/galaxyproject/tools-iuc/blob/master/.github/workflows/
    • [ ] https://github.com/galaxyproject/tools-devteam/blob/master/.github/workflows/

• [ ] Create Release Notes

  • [ ] Review merged PRs and ensure they all have a milestones attached. Link

  • [ ] Checkout release branch

    git checkout release_23.1 -b 23.1_release_notes

  • [ ] Bootstrap the release notes

    make release-bootstrap-history RELEASE_CURR=23.1

  • [ ] Open newly created files and manually curate major topics and release notes.
  • [ ] Run python scripts/release-diff.py release_23.0 and add configuration changes to release notes.
  • [ ] Add new release to doc/source/releases/index.rst

  • [ ] Commit release notes.

    git add docs/; git commit -m "Release notes for 23.1"; git push upstream 23.1_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=23.1

  • [ ] Ensure all blocking milestone PRs have been merged or closed.

    make release-check-blocking-prs RELEASE_CURR=23.1

  • [ ] Ensure all PRs merged into the pre-release branch during the freeze have milestones attached and that they are the not 23.2 milestones

  • [ ] Ensure release notes include all PRs added during the freeze by re-running the release note bootstrapping:

    make release-bootstrap-history

  • [ ] Ensure previous release is merged into current. GitHub branch comparison

  • [ ] Create and push release tag:

    make release-create

  • [ ] Create dev packages:

    cd packages && ./build_packages.sh

  • [ ] Review created packages (HISTORY.rst correct, setup.cfg correct, correct version in filename)

  • [ ] Upload built packages to pypi

  • [ ] Add the branch */release_{version} to Jenkins documentation build configuration matrix.

  • [ ] Trigger the branch documentation build

  • [ ] Verify that everything is merged from 23.1->master, and then trigger the 'latest' documentation build

• [ ] Do Docker Release

  • [ ] Change the dev branch of the Galaxy Docker container to 23.2
  • [ ] Merge dev into master

• [ ] 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/23.1_announce.rst
  • [ ] Stage announcement content (Hub, Galaxy Help, etc.) on announce date to capture date tags. Note: all final content does not need to be completed to do this.
  • [ ] Create hub highlights and post as a new "news" content item. An example.
  • [ ] Tweet docs news highlights link as @galaxyproject on twitter. An example.
  • [ ] Post highlights with tags news and release to Galaxy Help. 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 at https://github.com/galaxyproject/galaxy-hub/

• [ ] Prepare for next release

  • [ ] Close milestone 23.1 and ensure milestone 23.2 exists.
  • [ ] Create release issue for next version make release-issue.
  • [ ] Schedule committer meeting to discuss re-alignment of priorities.
  • [ ] Close this issue.

[dannon]

(This was supposed to be for 23.2)