-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated release notes for 1.7.0 #988
Merged
Merged
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
# Release Manager Actions Checklist Template | ||
|
||
| | | | ||
| --- |--| | ||
| Release version | 1.7.0 | | ||
| Next dev version | 1.8.0-SNAPSHOT | | ||
|
||
## Release Process Overview | ||
This is the full detailed release process, including the steps that are performed by the GitHub automation: [Release](../dev/release.md) | ||
|
||
## Pre-release | ||
|
||
- [x] Identify the version to be utilized for the release. | ||
- [x] Ensure all code commits and PRs intended for the release have been merged. | ||
- [x] 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](../dev/release-steps-with-automations.md) | ||
|
||
## Release Projects | ||
|
||
[Release All Modules Workflow](https://github.com/eclipse-pass/main/actions/workflows/pass-complete-release.yml) | ||
|
||
- [x] Release Main | ||
- [x] Release Pass-Core | ||
- [x] Release Pass Support | ||
- [x] Release Pass UI | ||
- [x] Release Pass Acceptance Testing | ||
- [x] Release Pass Docker | ||
|
||
## Post-release | ||
|
||
- [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. | ||
- [x] Check that correct tickets are in the release milestone. [GitHub Ticket Update](../dev/release.md#update-release-notes) | ||
- [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. | ||
- [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. | ||
- [ ] Post a message about the release to the PASS Google Group. [Notes about the PASS Google Group](../dev/release.md#process) | ||
- [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. | ||
- [ ] 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` | ||
- [ ] Send message to Eclipse PASS slack #pass-dev channel that the release is complete. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest adding a sentence or two here about the documentation work that was completed during this release (doc review manual, style guide, first-round of review). Maybe also note the background work happening to transition to Terraform.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. That makes sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done