azagrebin commented on a change in pull request #18: URL: https://github.com/apache/flink-docker/pull/18#discussion_r420860393
########## File path: README.md ########## @@ -24,6 +24,17 @@ Flink Docker image lifecycle https://github.com/docker-library/official-images/blob/master/library/flink). +Development workflow +---------------------------- + +The `master` branch of this repository serves as a pure publishing area for releases. + +Development happens on the various `dev-X` branches. + +Pull requests for a specific version should be opened against the respective `dev-<version>` branch. +Pull requests for all versions, or for the next major Flink release, should be opened against the `dev-master` branch. Review comment: It would be nice to add some details about which flink dist is tested by CI on dev branches. It looks that the `dev-1.X` branches run CI always against the last release and not its snapshots, like in `dev-master`, do we want this? This makes sense to check changes for generating other Dockerfile for the current patch release but it does not prepare for the next patch release using major release snapshots ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
