main

Release Manager Actions Checklist Template

Release version
Next dev version

Release Process Overview

This is the full detailed release process, including the steps that are performed by the GitHub automation: Release

Pre-release

• Identify the version to be utilized for the release.
• Ensure all code commits and PRs intended for the release have been merged.
• Issue a code freeze statement on the Eclipse PASS slack #pass-dev channel to notify all developers that a release is imminent.

Release Steps with Automations

Release Projects

Release All Modules Workflow

• Release Main
• Release Pass-Core
• Release Pass Support
• Release Pass UI
• Release Pass Acceptance Testing
• Release Pass Docker

Post-release

• Test the release by using the acceptance test workflow. Enter the release number into the Ref field.
• Check that correct tickets are in the release milestone. GitHub Ticket Update
• Write release notes in the Release Notes doc, submit a PR for the changes, and ensure the PR is merged. Release Notes should be written to be understandable by community members who are not technical.
• Draft release message and have technical & community lead provide feedback. Ensure that a link to the release notes is included in the release message.
• Post a message about the release to the PASS Google Group. Notes about the PASS Google Group
• Update template if any steps were missed or if any new tasks were added. Also make note of these new steps in the release-actions-X.X.X.md file.
• Update Pass Demo to new release - Publish to SNS Topic action using Environment: demo
• Send message to Eclipse PASS slack #pass-dev channel that the release is complete.

This site is open source. Improve this page.