Another case where this would've been useful...

In T282515#7081935, @JStephenson wrote:

Do you know where my manager has to authorise this?

In T282515#7081800, @JStephenson wrote:

I am still trying to access my WikiTech account but it says that I do not have access. Can you let me now what else I have to do?

I can't say I'd seen it been used in the wild. But the fact numerous other tasks exist, shows there's various holes to be plugged too. See also T282453: Allow to render WebP thumbnails in addition to PNG/JPG in MediaWiki core

Looks like IPUtils and purtle left. Purtle needs a release

I think so, yeah. Can't say 100% offhand, but should be cheap to try it, merge and see/confirm if it works correctly on beta

Yeah... That's not going to work. While the extension.json files are loaded as per wmf-config extension-list, there's no injection/loading of PHP classes into the autoloader for this to work as designed.

In T277955#7075080, @cjming wrote:

1. There are references to images that will be renamed as a part of this patch but they don't seem to reside in the codebase. Presumably wherever they are fetched from will need to rename these files accordingly. How/where does one take care of this?

In T277987#7068448, @JeffreyWang wrote:

Sorry if this is the wrong venue to voice this: so, for $wgWhitelistRead, what will be the phase-out process look like? Is there a proposed name for it like $wgAllowlistRead? And I would assume $wgWhitelistRead would be deprecated for a few versions of MediaWiki too. Same question goes for the rest of the LocalSettings.php config options which aren't simple internal core fixes.

It was more for cross linking purposes of related tasks. I wasn't saying "this is a duplicate".

T27611: Support optimized WebP thumbnails as alternative to JPEG, PNG, T269946: Enable webp thumbnails on all images for non-Commons wikis

As per https://www.mediawiki.org/wiki/Extension:Kartographer

Which packages are we using? Wikimedia apt? Debian? Sury?

Some side effect of rCICF676f3ec9891c: dockerfiles: Follow-up 49281f5fd and actually cascade these updates/rCICF49281f5fd7a1: dockerfiles: update sury.org GPG release key ?

Feels... Regression esque. But is it?

I think there's also some duplication of data (potentially a compressed and a non compressed version). So some time spent looking at that (though, I don't know who has access to it these days as since Chase left, no one on the team has root) could help slim the dataset down too.

I've brought it up on the security team channel about ressurecting T246954/T247492, and working out what to do longer term for this sort of data storage.

In T281203#7036804, @ArielGlenn wrote:

The discrepancy on the hosts is because /srv/dumps/security has 5.5T on the one host and doesn't exist on the other. Guess their team ought to be roped in on this discussion.

https://www.mediawiki.org/wiki/Manual:CleanupAncientTables.php needs updating...

I don't think there's anything to backport...? 1.37.0-wmf.3 is on every wiki, and stable. So it's just the config change to be deployed

Nope

Apparently I wrote this in 2012. Why, or for what exactly, I'm not sure. It was labelled as being WIP - rMW25017c83e13c: Work in progress (can kill another patch hanging around in my working copy)

Yeah. It was more an answer to your "Did we ever do a stand-alone upcoming EOL announcement/reminder?"

Haha. Probably. Not worth the extra hassle.

More usually it's been tacked onto another email that was being sent at the right time - https://lists.wikimedia.org/pipermail/mediawiki-announce/2020-September/000259.html

It might just be easier to provide a link saying "sign up for mediawiki-announce" but I doubt we'd get the same conversion rate.

Are there standards for licensing? For instance, is there programatic shorthand for "CC BY-SA". Tagging @mwilliams @Seddon on this in case they know.

Tarballs are staged and the 1.36.0-rc.0 tag is pushed.

I thought all SRE automagically get security@ as they also go to one of the SRE aliases?

This will require a MW core patch that accepts (read: does not filter out) FS file creation option header X-Delete-After.

In T281193#7035991, @Ostrzyciel wrote:

Phan in LTS branches, pretty-please?

Support HTTP/3 where? In MediaWiki? On Wikimedia Wikis? Both? Support it how?

For confirmation, was this just review of the MW extension? Or does it include the various services etc? Or just the external interactions (GET etc) with those services?

In T281072#7032260, @DannyS712 wrote:

In T281072#7032256, @Reedy wrote:

Pick your dupe: T275432: MassMessage not delivering, T255135: MassMessage delivery not taken place

Both of those are older tasks and mass messages were successfully being delivered between when those occurred and when this occurred, so it suggests that the issues have different causes