adoroszlai commented on pull request #22: URL: https://github.com/apache/ozone-docker/pull/22#issuecomment-981873748
@errose28 As far as I know `ozone-X` branches trigger image creation in Docker Hub with tag `X`, while `latest` does not. I'm not sure why we need both `latest` and `ozone-latest`. One reason might be to avoid triggering rebuild of `latest` image for changes that do not affect the image. For example most recently the addition of a `NOTICE` file, which is not copied into the image, hence does not change it. We should probably merge `ozone-latest` into `latest` to update with the 1.1.0 changes. After that, the changes for 1.2.0 (this PR) can be targeted at either of the two branches. Since `latest` is the default branch, I think we might want to prefer that as target. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
