Talk:Release checklist

Previous page history was archived for backup purposes at Talk:Release checklist/LQT Archive 1 on 2015-07-10.

These updates happen separately, as part of Security releases.

Is this checklist the right place to include updates to this table of version numbers, or do those decisions happen outside the release checklist?

Generally those are outside the release checklist; they're more for planning out releases in future, and marking EOL ones as they happen, and so are done as part of the Security releases.

Could someone who knows add updating at the right place, please? TIA

If you mean "please fiddle with Module:Version to tell it that REL1_37 has been branched as is a beta now, and 1.38 is the current master/alpha", then done. :-)

(If you mean something else, sorry, not sure what you mean.)

Heh, thanks! (Looks like Module:Version is already covered in the docs; it wasn't clear to me that this is the one to change.)

Should there be a dedicated item for major releases about [filing a task about] creating a Docker image, like https://phabricator.wikimedia.org/T213529 ?

If we do it, we should do it correct from the beginning and automate it, which would mean some subtask of https://phabricator.wikimedia.org/T156445

I think it should be up to the maintainers of the Docker image to keep on top of it (and they already do).

For automating docker specifically, we discussed it on https://github.com/wikimedia/mediawiki-docker/pull/36 but never finished the implementation.

And Debian has its own system of detecting new upstream releases: https://qa.debian.org/cgi-bin/watch?pkg=mediawiki