Thank you, that is excellent. Adding the last few release manager, they would have the most applicable feedback: @Kiley Sok <kiley...@google.com> @Robert Burke <r...@google.com> @Chamikara Jayalath <chamik...@google.com>
On Thu, Nov 10, 2022 at 1:17 PM Fer Morales Martinez < fernando.mora...@wizeline.com> wrote: > Hi everyone, > We would like to share with you that the team @ Wizeline will start > working on the migration of some of the tasks related to the release > process, detailed in [1]. > > For example, in the following PR [2] a workflow was created to execute, > within GitHub Actions (GHA), step 6 [3] of the release tasks. > > A similar effort is being worked on in this PR [4] to migrate step 8 [5] > to GHA. > > The initial approach will be to migrate the tasks that do NOT require the > use of keys to sign artifacts. The goal is to eventually replace the > locally executed tasks for tasks executed in GHA. > > The tasks which require keys and signing will still be executed locally > for the time being. > > We would love to receive any feedback or suggestion if any. > > Thanks! > > [1] https://beam.apache.org/contribute/release-guide > [2] https://github.com/apache/beam/pull/23390 > [3] > https://beam.apache.org/contribute/release-guide/#6-verify-release-branch > [4] https://github.com/apache/beam/pull/24075 > [5] > https://beam.apache.org/contribute/release-guide/#tag-a-chosen-commit-for-the-rc > > -- > > Fernando Morales (He/Him) | <https://www.wizeline.com/> | wizeline.com > <https://www.wizeline.com/> > > Software Engineer > > fernando.mora...@wizeline.com > > Remote Office, Mexico > > > > > > > > > *This email and its contents (including any attachments) are being sent > toyou on the condition of confidentiality and may be protected by > legalprivilege. Access to this email by anyone other than the intended > recipientis unauthorized. If you are not the intended recipient, please > immediatelynotify the sender by replying to this message and delete the > materialimmediately from your system. Any further use, dissemination, > distributionor reproduction of this email is strictly prohibited. Further, > norepresentation is made with respect to any content contained in this > email.*
