Thank you. I understand about a third of what you wrote. In a few years I
hope that I'll know enough about MediaWiki and release engineering to
understand 90% of the content of reports like that one.
I think in the future I'll start email chains like this one with a subject
line like "Once more
Already done:
https://wikitech.wikimedia.org/wiki/Incident_documentation/20170111-multiversion
-Chad
On Thu, Jan 12, 2017 at 8:27 AM Chad wrote:
> Yeah, I need to write one up, I'll try to get it done today or tomorrow.
>
> There won't be much to learn / do as a
Yeah, I need to write one up, I'll try to get it done today or tomorrow.
There won't be much to learn / do as a result, but it needs to be
documented at the very least.
-Chad
On Thu, Jan 12, 2017 at 8:18 AM Pine W wrote:
> Understood. Thanks for your efforts and the quick
Understood. Thanks for your efforts and the quick rollback. These things
happen sometimes, despite best efforts. When you have time to write an
incident report, I'd like to read it in the hope that I might learn
something from it, and perhaps others will as well.
Pine
On Thu, Jan 12, 2017 at
So this was my fault. I've been working on an ongoing effort to clean up
our multiversion code in wmf-config (this is the piece that allows us to run
different versions on different wikis).
Despite rigorous testing in beta & on the production debug servers, the
patch failed. I rolled back within
Thanks Florian. I'm curious to know what happened. When you have a
minute, perhaps
you could point me to the phab ticket or incident report.
Pine
On Wed, Jan 11, 2017 at 11:44 AM, Florian Schmidt <
florian.schmidt.wel...@t-online.de> wrote:
> It's already fixed, thanks for reporting!
>
>