errose28 commented on pull request #22: URL: https://github.com/apache/ozone-docker/pull/22#issuecomment-982061201
> As far as I know ozone-X branches trigger image creation in Docker Hub with tag X, while latest does not. This makes sense, thanks for the explanation. > 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. We want `ozone-latest` and `ozone-1.2.0` pointing at the same commit after this PR, right? So I think doing what you mentioned will work, and after merging this PR fast-forward `ozone-latest` to `latest` and create `ozone-1.2.0` off `latest`. So now it looks like the intended flow is to merge all changes to `latest`, and fast-forward `ozone-latest` when we want to do a docker hub release. However, since 1.1.0 went in to `ozone-latest` (probably by mistake), it won't be a fast-forward this time but a regular merge like you mentioned. -- 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]
