You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "tvalentyn (via GitHub)" <gi...@apache.org> on 2023/02/28 00:47:09 UTC
[GitHub] [beam] tvalentyn opened a new issue, #25653: [Task]: Document guidelines for how version guards should be specified for Beam dependencies
tvalentyn opened a new issue, #25653:
URL: https://github.com/apache/beam/issues/25653
### What needs to happen?
We should document this in install_requires and potentially in contributor guide and/or release guide sections of developer docs and have some process that enforces absence of obvious mistakes such as:
- depending on an exact version of a dependency.
- specifying '<=' in upper bound instead of a strict '<'.
- omitting explanations for non-obvious choices, such as a too open or too narrow range.
It might be possible to have a unit test or release validation script that automatically verifies some of that.
### 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: github-unsubscribe@beam.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [beam] tvalentyn commented on issue #25653: [Task]: Document guidelines for how version guards should be specified for Beam dependencies
Posted by "tvalentyn (via GitHub)" <gi...@apache.org>.
tvalentyn commented on issue #25653:
URL: https://github.com/apache/beam/issues/25653#issuecomment-1447430000
related: https://beam.apache.org/contribute/dependencies/
--
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: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [beam] tvalentyn commented on issue #25653: [Task]: Document guidelines for how version guards should be specified for Beam dependencies
Posted by "tvalentyn (via GitHub)" <gi...@apache.org>.
tvalentyn commented on issue #25653:
URL: https://github.com/apache/beam/issues/25653#issuecomment-1672419651
Content (for self reference) https://docs.google.com/document/d/1euZogGjbW4VZNJMFrA5AL1keR5gZO5l45H9b9CoQ0SI/edit
--
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: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [beam] tvalentyn commented on issue #25653: [Task]: Document guidelines for how version guards should be specified for Beam dependencies
Posted by "tvalentyn (via GitHub)" <gi...@apache.org>.
tvalentyn commented on issue #25653:
URL: https://github.com/apache/beam/issues/25653#issuecomment-1447360733
subtask of #25652
--
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: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org