Skip to content

Publication of Galaxy Release v 22.6 #2

@jdavcs

Description

@jdavcs
  • Prep

    • Create this release issue make release-issue.
    • Set freeze date (2025-01-01 00:00:00).
    • Verify that your installed version of galaxy-release-util is up-to-date.
  • Branch Release (on or around 2025-01-01 00:00:00)

    • Ensure all blocking milestone pull requests have been merged, closed, or postponed until the next release.

      make release-check-blocking-prs
      
    • Add latest database revision identifier (for release_22.6 and 22.6) 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_22.5
      make release-push-dev
      
    • Create and push release branch:

      make release-create-rc
      
    • Open pull requests from your fork of branch version-22.6 to upstream release_22.6 and of version-22.53.dev to dev.

    • Update MILESTONE_NUMBER in the maintenance bot to 22.53 so it properly tags new pull requests.

  • Issue Review Timeline Notes

    • Ensure any security fixes will be ready prior to 2025-01-01 00:00:00 + 1 week, to allow time for notification prior to release.
    • Ensure ownership of outstanding bugfixes and track progress during freeze.
  • Deploy and Test Release

  • Create Release Notes

    • Review merged pull requests and ensure they all have a milestone attached. Link

    • Switch to release branch and create a new branch for release notes

      git checkout release_22.6 -b 22.6_release_notes
      
    • Bootstrap the release notes

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

    • Run python scripts/release-diff.py release_22.5 and add configuration changes to release notes.

    • Add new release to doc/source/releases/index.rst

    • Open a pull request for the release notes branch.

    • Merge release notes pull request.

  • Do Release

    • Ensure all blocking milestone issues have been resolved.

      make release-check-blocking-issues RELEASE_CURR=22.6
      
    • Ensure all blocking milestone pull requests have been merged, closed, or postponed until the next release.

      make release-check-blocking-prs RELEASE_CURR=22.6
      
    • Ensure all pull requests merged into the pre-release branch during the freeze have milestones attached and that they are the not 22.53 milestones

    • Ensure release notes include all pull requests 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
      
    • Create the first point release (v22.6.0) using the instructions at https://docs.galaxyproject.org/en/master/dev/create_point_release.html

    • Open PR against planemo with a pin to the new packages

  • Announce Release

  • Prepare for next release

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions