If you are not an extension developer, you can safely ignore this message.
I am excited to announce that the Minerva Neue skin will be bundled with
MediaWiki in 1.38 per https://phabricator.wikimedia.org/T191743
The Minerva Neue skin powers the mobile site of Wikimedia projects, so it
makes sense to include this skin for 3rd party MediaWiki instances that
want a responsive but simplified experience.
The implication of this is that extension developers should be making sure
their code compatible with MinervaNeue.
Note, that Minerva Neue operates in two modes (a desktop or mobile mode)
depending on whether MobileFrontend is installed, however, MobileFrontend
is still not part of the MediaWiki bundle so this mode doesn't need to be
tested at this point.
You can tell if you are in Minerva desktop mode by testing in an incognito
window and verifying that you see a more (ellipsis) dropdown in the toolbar.
e.g. Test on https://en.wikipedia.org/wiki/Minerva?useskin=minerva NOT
if you have any questions or concerns please feel free to reply to this
e-mail or the Phabricator ticket.
Thanks for reading!
🚂🌈Summary of 1.38.0-wmf.16 train deployment
This email is a summary of the Wikimedia production deployment of
*wmf.16* is in production across all wikis and I'll be handing the
conductor hat to Dan for *wmf.17* which starts rolling today.
- Conductor: Mukunda Modell
- Backup Conductor: Antoine "hashar" Musso
- Blocker Task: T293957 <https://phabricator.wikimedia.org/T293957>
- Current Status <https://versions.toolforge.org>
Stats for this train compared to the last 5 trains.
- 483 patches ▁▃▂▂█
- 0 Rollbacks █▆▃▆▁
- 1 Days of delay ▆█▁▂▂
- 4 Blockers ▁█▇▅▄
🎉 Traintastic Folks 🎉 Thanks to folks who reported or resolved blockers:
- James D. Forrester
- Timo Tijhof
- Ed Sanders
MediaWiki has an experimental configuration flag $wgUseCategoryBrowser that
alters the appearance of categories. If you don't use this flag or are not
aware of it you can safely ignore this message.
We plan to remove this configuration flag and associated code in MediaWiki
1.38 without deprecation warnings given its experimental nature:
If needed an extension can provide the same functionality, so if anyone
needs this functionality please let us know by replying to this email or
the Phabricator ticket to help guide us better.
Thanks for reading
If you don’t use tendril.wikimedia.org or dbtree.wikimedia.org, feel free
to ignore this message.
As of today, tendril is now retired and the main page is replaced with a
list of replacement for different services tendril used to provide:
For checking out our dbtree and replication data:
if you are in the NDA LDAP group, use Orchestrator
otherwise, use the information page <https://noc.wikimedia.org/db.php>
on noc.wikimedia.org. For more detail you can also check eqiad.json
<https://noc.wikimedia.org/dbconfig/eqiad.json> or codfw.json
If you are looking for slow queries log, go to slow queries dashboard
using our standard observability platform (logstash) (NDA required)
Tendril has been a great tool for us during the years, but unfortunately it
is impossible to maintain with modern MariaDB versions (it uses TokuDB,
which is no longer available on MariaDB after 10.1 and needs to be compiled
separately) nor its webservice is compatible with modern php versions. Its
database is still running on Stretch and on MariaDB 10.1 (which has not
been supported for a year already) and it is having serious scalability
issues. This would unblock us from removing a lot of legacy home-brew craft
and replace them with more modern toolings such as orchestrator
Orchestrator has been in place for a few months now, and provides us with a
great way to see and (in the future) manage replication topologies. For now
we are using it only for visualization purposes but in the future we’d like
it to also help us to handle replication changes (it can be done from the
UI or via CLI) and recover topologies automatically if they fail and
involve masters or intermediate masters.
The slow queries dashboard
in logstash offer multiple advantages over tendril. You can set the
threshold to see slow queries that took longer to run. You can filter out
code paths you’re not interested in or zoom in to relevenet code paths. You
can limit it to write queries or read queries only. Also, it provides id of
the request making the slow query, so you can cross check it with the rest
of logstash or hadoop to identify problematic behavior.
If you need it for the transition period, you can still access it in
tendril-legacy.wikimedia.org. But it will be shut down in a month. You can
follow the work of shutting down tendril in