I'm +1 on RC1 based on the 7 tests I know I can check successfully. I'll be trying more tomorrow, but remember that release validation requires the community to validate it meets our standards, and I can't do it alone.
Remember you can participate in the release validation by reviewing parts of the documentation being published as well, not just by running the Pyhton and Java artifacts. If you have contributed new python or java docs into this release, they'll appear in the to be published docs. Cheers, Robert Burke 2.26.0 release manager On Mon, Dec 7, 2020, 6:25 PM Robert Burke <rob...@frantil.com> wrote: > Turns out no changes required affecting the dataflow artifacts this time > around, so Dataflow is cleared for testing. > > Cheers. > Robert Burke > 2.26.0 Release Manager > > On Mon, Dec 7, 2020, 6:03 PM Robert Burke <r...@google.com> wrote: > >> >> Robert Burke <r...@google.com> >> Thu, Dec 3, 8:01 PM (4 days ago) >> to dev >> Hi everyone, >> Please review and vote on the release candidate #1 for the version >> 2.26.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. >> >> The complete staging area is available for your review, which includes: >> * JIRA release notes [1], >> * the official Apache source release to be deployed to dist.apache.org [2], >> which is signed with the key with fingerprint >> A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3], >> * all artifacts to be deployed to the Maven Central Repository [4], >> * source code tag "v2.26.0-RC1" [5], >> * website pull request listing the release [6], publishing the API >> reference manual [7], and the blog post [8]. >> * Java artifacts were built with Maven 3.6.0 and OpenJDK 1.8.0_275. >> * Python artifacts are deployed along with the source release to the >> dist.apache.org [2]. >> * Validation sheet with a tab for 2.26.0 release to help with validation >> [9]. >> * Docker images published to Docker Hub [10]. >> >> The vote will be open for at least 72 hours (10th ~6pm PST). It is >> adopted by majority approval, with at least 3 PMC affirmative votes. >> >> Thanks, >> Robert Burke >> 2.26.0 Release Manager >> >> [1] >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12348833 >> [2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/ >> [3] https://dist.apache.org/repos/dist/release/beam/KEYS >> [4] https://repository.apache.org/content/repositories/org apache >> beam-1144/ >> [5] https://github.com/apache/beam/tree/v2.26.0-RC1 >> [6] https://github.com/apache/beam/pull/13481 >> [7] https://github.com/apache/beam-site/pull/609 >> [8] https://github.com/apache/beam/pull/13482 >> [9] >> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=475997301 >> [10] https://hub.docker.com/search?q=apache%2Fbeam&type=image >> >> PS. New Dataflow artifacts likely need to be built and published but this >> doesn't block vetting the remainder of the RC at this time. Thank you for >> your patience. >> >>
