I tried running a Dataflow Python pipeline on RC1 and got an error: Pipeline construction environment and pipeline runtime environment are not compatible. If you use a custom container image, check that the Python interpreter minor version and the Apache Beam version in your image match the versions used at pipeline construction time. Submission environment: beam:version:sdk_base:apache/beam_python3.11_sdk:2.50.0rc1. Runtime environment: beam:version:sdk_base:apache/beam_python3.11_sdk:2.50.0. Worker ID: beamapp-valentyn-08220117-08211817-m76c-harness-v38w
Opened https://github.com/apache/beam/issues/28084 to track. On Mon, Aug 21, 2023 at 10:02 AM Robert Burke <lostl...@apache.org> wrote: > Hi Beamers, > > Today I'm working on the aforementioned gaps in this RC blocking. > > However, it's still valuable to validate and vote on the remainder of the > RC in order to ensure a timely 2.50.0 release, and finding whether we'll > need an RC2 or not. > > Robert Burke > Apache Beam 2.50.0 Release Manager > > On 2023/08/18 00:58:00 Robert Burke wrote: > > Hi everyone, > > Please review and vote on the release candidate #1 for the version > 2.50.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]. > > > > Additional notes about this RC: > > > > * There were issues in starting Dataflow clones portable containers to > > Google Container Repository and Google Artifact Registry, so those images > > may not yet be available at those locations, which may impact starting > jobs > > with the RC against Google Cloud Dataflow. > > * This may be worked around by explicitly setting the portable > container > > to use with the --sdkContainerImage flag for Java, or the > > --environment_config flag for Python and Go. > > * Due to an issue with my build environment, there were issues producing > > two artifacts for this RC. > > * The Typescript SDK container has not yet been built or pushed. As an > > experimental SDK this is not a release blocker. However, one will > > eventually be published. In the meantime, the 2.49.0 container should be > > sufficient. > > * Due to an issue with my build environment, the PyDocs are not > currently > > part of the Documentation PR update. This will block the final release > of > > 2.50.0 > > * The current plan is to spend improve the Github Actions for releases > to > > be able to provide these artifacts, instead of performing a local fix to > my > > environment, to simplify further releases. > > > > > > The 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 02677FF4371A3756 ( > > lostl...@apache.org) or D20316F712213422 > > (GitHub Action automated) [[3], > > * all artifacts to be deployed to the Maven Central Repository [4], > > * source code tag "v2.50.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 7.5.1 and OpenJDK (Temurin)(build > > 1.8.0_382-b05). > > * 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.50.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 https://beam.apache.org/blog/validate-beam-release/. > > > > Thanks, > > Robert Burke > > Apache Beam 2.50.0 Release Manager > > > > [1] https://github.com/apache/beam/milestone/14 > > [2] https://dist.apache.org/repos/dist/dev/beam/2.50.0/ > > [3] https://dist.apache.org/repos/dist/release/beam/KEYS > > [4] > https://repository.apache.org/content/repositories/orgapachebeam-1353/ > > [5] https://github.com/apache/beam/tree/v2.50.0-RC1 > > [6] https://github.com/apache/beam/pull/28055 > > [7] https://github.com/apache/beam-site/pull/647 > > [8] https://pypi.org/project/apache-beam/2.50.0rc1/ > > [9] > > > https://pkg.go.dev/github.com/apache/beam/sdks/v2@v2.50.0-RC1/go/pkg/beam > > [10] > > > https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid= > . > > .. > > [11] https://hub.docker.com/search?q=apache%2Fbeam&type=image > > [12] https://github.com/apache/beam/pull/27962 > > >
