Skip to content

Commit 44d01b3

Browse files
authored
Create release-actions-1.8.0.md
1 parent 6ba3a5f commit 44d01b3

File tree

1 file changed

+39
-0
lines changed

1 file changed

+39
-0
lines changed

docs/release/release-actions-1.8.0.md

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
# Release Manager Actions Checklist Template
2+
3+
| | |
4+
| --- |--|
5+
| Release version | 1.8.0 |
6+
| Next dev version | 1.9.0-SNAPSHOT |
7+
8+
## Release Process Overview
9+
This is the full detailed release process, including the steps that are performed by the GitHub automation: [Release](../dev/release.md)
10+
11+
## Pre-release
12+
13+
- [x] Identify the version to be utilized for the release.
14+
- [x] Ensure all code commits and PRs intended for the release have been merged.
15+
- [x] Issue a code freeze statement on the Eclipse PASS slack #pass-dev channel to notify all developers that a release is imminent.
16+
17+
[Release Steps with Automations](../dev/release-steps-with-automations.md)
18+
19+
## Release Projects
20+
21+
[Release All Modules Workflow](https://github.com/eclipse-pass/main/actions/workflows/pass-complete-release.yml)
22+
23+
- [x] Release Main
24+
- [x] Release Pass-Core
25+
- [x] Release Pass Support
26+
- [x] Release Pass UI
27+
- [x] Release Pass Acceptance Testing
28+
- [x] Release Pass Docker
29+
30+
## Post-release
31+
32+
- [x] Test the release by using the [acceptance test workflow](https://github.com/eclipse-pass/pass-acceptance-testing/actions/workflows/test.yml). Enter the release number into the Ref field.
33+
- [x] Check that correct tickets are in the release milestone. [GitHub Ticket Update](../dev/release.md#update-release-notes)
34+
- [x] Write release notes in the [Release Notes doc](../release-notes.md), 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.
35+
- [x] Draft release message and have technical & community lead provide feedback. Ensure that a link to the release notes is included in the release message.
36+
- [x] Post a message about the release to the PASS Google Group. [Notes about the PASS Google Group](../dev/release.md#process)
37+
- [x] 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.
38+
- [x] Update [Pass Demo](https://demo.eclipse-pass.org) to new release - [Publish to SNS Topic action](https://github.com/eclipse-pass/main/actions/workflows/deployToAWS.yml) using `Environment: demo`
39+
- [x] Send message to Eclipse PASS slack #pass-dev channel that the release is complete.

0 commit comments

Comments
 (0)