daniel-packard commented on PR #158: URL: https://github.com/apache/flink-docker/pull/158#issuecomment-1587654571
Hey @zentol - Right now we have two proposed changes on the table: 1. add symlinks from e.g. `1.16.jar` -> `1.16.2.jar` 2. add support for pattern matching e.g. `1.16.*.jar` I think we should try to decide between: - implement 1, - implement 2, - implement _both_, - implement _neither_ Both of the proposed changes would let the consumer of `flink:1.16` docker images ignore the detail of the patch version (e.g. `1.16.2`). So I think the first question we should answer is... Is it a reasonable request that "consumers of `flink:1.16` docker images" should be able to "ignore the detail of the patch version"? In my mind, the answer is "yes" - because if I wanted to worry about patch version, I would use a more specific docker base image (`flink:1.16.2`) But it's possible that safety/stability _demands_ that devs are aware of changing patch versions .... in which case the answer would be no.. But then I might ask why `flink:1.16` is even an option for a base image if we still have to worry about patch version changes? -- 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]
