Hi everyone, This is an update for the 2.49.0 release candidate validation.
There was one issue added to the milestone [1] since the creation of this thread that was regarding TypeScript container [2]. Also, two infrastructure fixes are integrated into the release branch [3, 4], both are part of the ongoing work of automating the release process and do not involve SDK code changes. This means there will be an RC2 to be tagged. Because the changes on the release branch since RC1 tag do not involve Java, Python, and Go SDK, I encourage continue the current release validations, and please use the spreadsheet [5] and add identified issues to the milestone [1] if any. I plan to tag RC2 3 weekdays after RC1 validation has started (that is around Jun 11) if there is no outstanding issue in the milestone [1] then. Thanks, Release Manager [1] https://github.com/apache/beam/milestone/13 [2] https://github.com/apache/beam/pull/27386 [3] https://github.com/apache/beam/pull/26967 [4] https://github.com/apache/beam/pull/27398 [5] https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=934901728 On Fri, Jul 7, 2023 at 10:50 AM Alexey Romanenko <aromanenko....@gmail.com> wrote: > +1 (binding) > > Tested with https://github.com/Talend/beam-samples/actions > (Java SDK v8/v11/v17, Spark 3.x runner). > > — > Alexey > > On 6 Jul 2023, at 17:34, Yi Hu via dev <dev@beam.apache.org> wrote: > > Hi everyone, > Please review and vote on the release candidate #1 for the version 2.49.0, > as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > > Reviewers are encouraged to test their own use cases with the release > candidate, and vote +1 if > no issues are found. Only PMC member votes will count towards the final > vote, but votes from all > community members is encouraged and helpful for finding regressions; you > can either test your own > use cases or use cases from the validation sheet [10]. > > The complete staging area is available for your review, which includes: > * GitHub Release notes [1], > * the official Apache source release to be deployed to dist.apache.org > [2], which is signed with the key with > fingerprint either CB6974C8170405CB (y...@apache.org) or D20316F712213422 > (GitHub Action automated) [3], > * all artifacts to be deployed to the Maven Central Repository [4], > * source code tag "v2.49.0-RC1" [5], > * website pull request listing the release [6], the blog post [6], and > publishing the API reference manual [7]. > * Java artifacts were built with Gradle GRADLE_VERSION and OpenJDK/Oracle > JDK JDK_VERSION. > * Python artifacts are deployed along with the source release to the > dist.apache.org [2] and PyPI [8]. > * Go artifacts and documentation are available at pkg.go.dev [9] > * Validation sheet with a tab for 2.49.0 release to help with validation > [10]. > * Docker images published to Docker Hub [11]. > * PR to run tests against release branch [12]. > > The vote will be open for at least 72 hours. It is adopted by majority > approval, with at least 3 PMC affirmative votes. > > For guidelines on how to try the release in your projects, check out our > blog post at /blog/validate-beam-release/. > > Thanks, > Release Manager > > [1] https://github.com/apache/beam/milestone/13 > [2] https://dist.apache.org/repos/dist/dev/beam/2.49.0/ > [3] https://dist.apache.org/repos/dist/release/beam/KEYS > [4] https://repository.apache.org/content/repositories/orgapachebeam-1348/ > [5] https://github.com/apache/beam/tree/v2.49.0-RC1 > [6] https://github.com/apache/beam/pull/27374 > [7] https://github.com/apache/beam-site/pull/646 > [8] https://pypi.org/project/apache-beam/2.49.0rc1/ > [9] > https://pkg.go.dev/github.com/apache/beam/sdks/v2@v2.49.0-RC1/go/pkg/beam > [10] > https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=934901728 > [11] https://hub.docker.com/search?q=apache%2Fbeam&type=image > [12] https://github.com/apache/beam/pull/27307 > > -- > Yi Hu, (he/him/his) > Software Engineer > > >
