tvalentyn opened a new issue, #25668: URL: https://github.com/apache/beam/issues/25668
### What needs to happen? The goal is to check that: 1) the latest Python SDK in PyPI is remains installable and usable if tomorrow some Beam's dependency promotes their currently available release candidate, to be a release. This suite should install apache-beam[gcp] from pypi, instead of using Beam's SDK tarball (dev SDK). Additionally, this test should install apache beam with `--pre` flag https://pip.pypa.io/en/stable/cli/pip_install/#install-pre. 2) Same as #1, but use Dev SDK, and install the new dependencies in Beam's docker containers. One way to add this scenario is to reuse a Dataflow Python ValidatesContainer test, but install Beam with `--pre` flag. ### Issue Priority Priority: 2 (default / most normal work should be filed as P2) ### Issue Components - [X] Component: Python SDK - [ ] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
