-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump stable tag to 28.0.6 or even to 29.0.3 #2252
Comments
Yes, I think it's an oversight that |
In regards to bumping to |
The policy used to be that, if not held back by an issue, the stable tag follows the 100% rollout state of the update-server. Since the update server gets polled by all instances that then nudge their admins to update. That's also why I linked the commits above. But maybe I missed a change in policy for the docker image. |
Thanks for bumping the tag to 28.07. Is there an issue/a discussion that blocks 29? |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
ah sure, we can upgrade that with the next release or so. |
Hello,
since 25th Jun the rollout of Version 28.0.6 is the 100% rolled out version of V28 (with this commit: update-server-commit
But even earlier this commit update-server-commit from the 23th of may the rollout from 28 to 29 was set to 100%.
Would it make sense to bump the stable tag to 28.0.6 or even to the right now 100% rolled out version of 29.0.3?
Or is there a bug blocking this?
Sorry that I always ask, but there seems to be no such overview available.
Otherwise I could look into and of possible help to work on them.
Or would it make sense to open Pull-Requests for bumping the stable version myself and then discuss possible blocking issues in the Pull-Request?
Thank you for the work on this container-image.
Best regards
The text was updated successfully, but these errors were encountered: