- Review, locally test, and merge: https://gerrit.wikimedia.org/r/c/performance/WikimediaDebug/+/641835/
- Release (see repo README)
|Resolved||None||T248925 Make MediaWiki release tarball compatible with PHP 8.0|
|Resolved||Jdforrester-WMF||T300463 Make PHP 8.0 voting on MW master|
|Resolved||Jdforrester-WMF||T313563 Bump lcobucci/jwt & league/uri-components for php8|
|Resolved||Jdforrester-WMF||T313564 Bump onoi/message-reporter in vendor.git to 1.4.2 for php 8 support|
|Resolved||Jdforrester-WMF||T247658 Make Wikimedia Production MediaWiki compatible with PHP 7.4|
|Resolved||• toan||T243590 Fix WikibaseDataModel CI for php 7.4|
|Resolved||Lucas_Werkmeister_WMDE||T316923 Restore skipped test in ReferenceListTest.php|
|Resolved||Joe||T318918 Undeploy patch to use old PHP serialization in PHP 7.4|
|Resolved||Jdforrester-WMF||T264168 Drop PHP 7.2 support from Wikibase master branch, once Wikimedia production is on 7.4|
|Resolved||Ladsgroup||T270740 Drop hacky support for doctrine/dbal class renaming|
|Invalid||None||T303505 [S] Remove Deprecated methods "serialize" and "unserialize" after php production upgrade to PHP 7.4|
|Resolved||Reedy||T251043 Cleanup css-sanitizer when it only requires PHP >= 7.4|
|Open||None||T166010 The Great Namespaceization and Reorg|
|Resolved||tstarling||T277618 var_dump() on various objects writes gigabytes of data and takes minutes to run|
|Resolved||Jdforrester-WMF||T261872 Drop PHP 7.2 & 7.3 support from MediaWiki master branch, once Wikimedia production is on 7.4|
|Stalled||None||T302086 Set scap minimum python version to 3.7|
|Open||None||T247045 Migrate all of production metal and VMs to Buster or later|
|Resolved||PRODUCTION ERROR||Legoktm||T293568 PHP Notice: Undefined offset in wikimedia/remex-html when rendering rest.php error page|
|Resolved||tstarling||T297667 mysqli/mysqlnd memory leak|
|Resolved||Joe||T271736 Migrate WMF production from PHP 7.2 to PHP 7.4|
|Resolved||Krinkle||T248191 Can't reopen table in wikidb-unittest_ (from SpecialPageFatalTest)|
|Open||None||T278203 Migrate all CI jobs from stretch to buster or later and drop stretch testing support|
|Resolved||Jdforrester-WMF||T252432 Drop MediaWiki testing in stretch and instead test only in buster|
|Resolved||Dzahn||T245757 Upgrade MediaWiki clusters to Debian Buster (debian 10)|
|Resolved||Dzahn||T267248 create mwdebug1003 - ganeti VM with buster and appserver role|
|Resolved||• Gilles||T268188 Release WikimediaDebug for mwdebug1003 addition|
@Krinkle where are the credentials for the chrome-wikimedia-debug Google account and the Firefox equivalent stored? I don't see any mention of it on the repo README or on the wiki page about the extension.
Both of those are tied to a group of one or more individual accounts. I've added your wikimedia.org address to the list of owners for the Chrome extension (which it manages through a google group called chrome-wikimedia-debug). However if you prefer your personal account (as I did), let me know and I'll add that instead.
For the Firefox one, let me know which account I should add there.
FYI, usage of Google Payments for my work account has to go through legal review, which is going to delay my ability to push this update to the Chrome store.
Maybe this time around @Krinkle you should push it for Chrome, I'll push it for Firefox and next time I'll do both? once ITS and Legal have figured out if/how we can pay Google $5...
If that works for you, I'll tag the new version and push it to Firefox.
I see the Firefox one has been reviewed and published meanwhile. The Chrome one should be done within a day as well, they've generally been quite quick.