kennknowles commented on issue #28811: URL: https://github.com/apache/beam/issues/28811#issuecomment-1755748439
We have to choose. Either: 1. We pin dependencies and we know that transitive dependencies cannot break users. 2. We do semver loose dependencies and know that transitive dependencies can break users. In scenario 2 we can't really treat transitive dependency changes as a panic situation or release blocker, because the behavior is actually by design. To be very clear: I like scenario 2 better and I think dependency pinning should wait until the final deployment of an application. For test coverage: Even though we claim we are compatible with a semver range, we have not tested that whole range. In reality it just means the same thing as being pinned to the top of the range. We have no idea if Beam 2.51.0 actually works with lower versions of fastavro. It was never tested. -- 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]
