Bump stable tag to 28.0.6 or even to 29.0.3

[Zottel92]

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

[te-online]

Yes, I think it's an oversight that stable is not updated to 28.0.7 yet, because it has always worked that way. Not sure who can fix this? @J0WI?

[te-online]

In regards to bumping to 29.0.3, I'm not sure if there are any guidelines on when a new version is stable enough for the stable tag, but I think there's plenty of life left in 28 (if we're looking at the Maintenance and Release Schedule, so I would expect an update of stable later this year.

[Zottel92]

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.
The "stable" state of a Version is therefore reached when all instances that want to update are asked to do so.

That's also why I linked the commits above. But maybe I missed a change in policy for the docker image.

[Zottel92]

Thanks for bumping the tag to 28.07.

Is there an issue/a discussion that blocks 29?
As written above 29 seems to be rolled out 100% already on the update server.

[J0WI]

ah sure, we can upgrade that with the next release or so.