lostluck opened a new pull request, #28287:
URL: https://github.com/apache/beam/pull/28287
This is a larger cleanup of the release guide to clarify timings and
positioning of the broader steps.
Larger emphasis has been put on the Release Manager's role prior to the
release cut. If issues are addressed in the main branch before the cut, they do
not need to be addressed afterwards. The release manager is empowered to do so.
Clarify some timing around the begining and end of the release by calling
out the preparation steps should be performed within the week prior to the
release cut. Also call out that release finalization tasks can be done within a
few hours of the release being completed.
While the guide isn't materially shorter, maintaining the simpler structure
as in the overview will make it less overwheling to release managers, since
it's clearer when the various subtasks apply, vs the previous "13" steps. This
should clarify the "build release candidate + vote + fix" loop that is the bulk
of a release manager's tasks. I believe this will help get to release
candidates sooner.
Add a new section "Post Release Tasks" which is where the Playground update
task lives. While it's part of the release tasks, it doesn't block the release
overall, so it felt weird structurally to have it as important as "Build a
Release Candidate".
Various minor typos and fixes.
------------------------
Thank you for your contribution! Follow this checklist to help us
incorporate your contribution quickly and easily:
- [ ] Mention the appropriate issue in your description (for example:
`addresses #123`), if applicable. This will automatically add a link to the
pull request in the issue. If you would like the issue to automatically close
on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead.
- [ ] Update `CHANGES.md` with noteworthy changes.
- [ ] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
See the [Contributor Guide](https://beam.apache.org/contribute) for more
tips on [how to make review process
smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier).
To check the build health, please visit
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
GitHub Actions Tests Status (on master branch)
------------------------------------------------------------------------------------------------
[](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule)
See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more
information about GitHub Actions CI or the [workflows
README](https://github.com/apache/beam/blob/master/.github/workflows/README.md)
to see a list of phrases to trigger workflows.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
