diff --git a/docs/release-notes.md b/docs/release-notes.md index 29b751d..087c681 100644 --- a/docs/release-notes.md +++ b/docs/release-notes.md @@ -1,3 +1,20 @@ +## Release v1.7.0 +### Date: May 30, 2024 + +Release Manager: Russ Poetker, JHU + +This release focused on adding a GitHub workflow that will complete the release of all PASS components. The pass-core metadata schema service was changed as a first step in supporting InvenioRDM integration. There were several documentation tasks completed such as a Review Manual, Style Guide, and first round of reviews. There has been steps made to eventually add IaC for PASS. OpenTofu has been selected as the IaC tool; developing the terraform modules is in progress. A few smaller bugs were also fixed. + +Tickets Completed: https://github.com/eclipse-pass/main/milestone/21?closed=1 + +Release Components: +* main - https://github.com/eclipse-pass/main/releases/tag/1.7.0 +* pass-core - https://github.com/eclipse-pass/pass-core/releases/tag/1.7.0 +* pass-docker - https://github.com/eclipse-pass/pass-docker/releases/tag/1.7.0 +* pass-acceptance-testing - https://github.com/eclipse-pass/pass-acceptance-testing/releases/tag/1.7.0 +* pass-support - https://github.com/eclipse-pass/pass-support/releases/tag/1.7.0 +* pass-ui - https://github.com/eclipse-pass/pass-ui/releases/tag/1.7.0 + ## Release v1.6.1 ### Date: May 7, 2024 @@ -22,7 +39,7 @@ Release Components: Release Manager: Mark Patton, JHU -This release focused on simplifying authentication support, writing documentation to make collaboration easier, and automated testing against a live PASS instance. The pass-core component took over the responsibilty for authentication and mediating access to pass-ui resources. This allowed us to to remove the no longer needed pass-auth component. The deposit services now also cleanup after the new automated tests. +This release focused on simplifying authentication support, writing documentation to make collaboration easier, and automated testing against a live PASS instance. The pass-core component took over the responsibility for authentication and mediating access to pass-ui resources. This allowed us to remove the no longer needed pass-auth component. The deposit services now also cleanup after the new automated tests. Tickets Completed: https://github.com/eclipse-pass/main/milestone/20?closed=1 diff --git a/docs/release/release-actions-1.7.0.md b/docs/release/release-actions-1.7.0.md new file mode 100644 index 0000000..883e36a --- /dev/null +++ b/docs/release/release-actions-1.7.0.md @@ -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. +- [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` +- [ ] Send message to Eclipse PASS slack #pass-dev channel that the release is complete. \ No newline at end of file diff --git a/docs/release/release-actions-template.md b/docs/release/release-actions-template.md index c8555ab..5e887a8 100644 --- a/docs/release/release-actions-template.md +++ b/docs/release/release-actions-template.md @@ -29,7 +29,7 @@ This is the full detailed release process, including the steps that are performe ## Post-release -- [ ] Test the release by using the newly updated pass-docker to run the release locally. +- [ ] 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. - [ ] Check that correct tickets are in the release milestone. [GitHub Ticket Update](../dev/release.md#update-release-notes) - [ ] 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. - [ ] Draft release message and have technical & community lead provide feedback. Ensure that a link to the release notes is included in the release message.