The process I have been following is [1]. I have also suggested edits to the voting email template to include the self-link. However, does anyone can edit this doc so the change can be made? Otherwise we might better to migrate this doc to https://github.com/apache/beam/tree/master/contributor-docs
[1] https://s.apache.org/beam-release-vendored-artifacts On Thu, Jan 18, 2024 at 2:56 PM Robert Bradshaw via dev <dev@beam.apache.org> wrote: > Could you explain the process you used to produce these artifacts? > > On Thu, Jan 18, 2024 at 11:23 AM Kenneth Knowles <k...@apache.org> wrote: > >> +1 >> >> On Wed, Jan 17, 2024 at 6:03 PM Yi Hu via dev <dev@beam.apache.org> >> wrote: >> >>> Hi everyone, >>> >>> >>> Please review the release of the following artifacts that we vendor: >>> >>> * beam-vendor-grpc-1_60_1 >>> >>> >>> Please review and vote on the release candidate #1 for the version 0.1, >>> as follows: >>> >>> [ ] +1, Approve the release >>> >>> [ ] -1, Do not approve the release (please provide specific comments) >>> >>> >>> The complete staging area is available for your review, which includes: >>> >>> * the official Apache source release to be deployed to dist.apache.org >>> [1], which is signed with the key with fingerprint 8935B943A188DE65 [2], >>> >>> * all artifacts to be deployed to the Maven Central Repository [3], >>> >>> * commit hash "52b4a9cb58e486745ded7d53a5b6e2d2312e9551" [4], >>> >>> The vote will be open for at least 72 hours. It is adopted by majority >>> approval, with at least 3 PMC affirmative votes. >>> >>> Thanks, >>> >>> Release Manager >>> >>> [1] https://dist.apache.org/repos/dist/dev/beam/vendor/ >>> >>> [2] https://dist.apache.org/repos/dist/release/beam/KEYS >>> >>> [3] >>> https://repository.apache.org/content/repositories/orgapachebeam-1366/ >>> >>> [4] >>> https://github.com/apache/beam/commits/52b4a9cb58e486745ded7d53a5b6e2d2312e9551/ >>> >>> >>> -- >>> >>> Yi Hu, (he/him/his) >>> >>> Software Engineer >>> >>> >>>
