Software updates Wednesday morning

I’ve been spending much of the last few work days tidying up an update to our deployed codebase, which has been several weeks behind development for most components.

I’ll want to start deploying this in the morning (Pacific time), so we’ll have most of the day to poke around and fix up any problems on the sites… it’s gonna be fun!

This’ll primarily bring a lot of under-the-hood improvements, which’ll let us start rolling out other fun things over the coming days/weeks including:

For those of you poking at the code, I’ve got the pre-deployment code currently sitting in the wmf-deployment-work branch; this’ll get folded back over wmf-deployment when we’re ready to go.

I believe all custom hacks from the current wmf-deployment branch have been either copied over or generalized and merged via trunk… Note I’ve held back updates on ProofreadPage and OggHandler for the moment, and we won’t deploy the new JS2 code yet until we’ve shaken things down some more.

If there are any *critical* trunk fixes from the last few days (since r55160 trunk branch point) that need to be forward-ported before we start, or any other surprises, let’s make sure we know about it soon. :)

– brion

Update 1:30 UTC Sep 17: Most problems have now been shaken out. Probably a few more minor glitches to go, then we can worry about prepping the fun stuff! :)

Brion Vibber, Lead Software Architect

9 Show

9 Comments on Software updates Wednesday morning

brion 5 years

And check again with those third-party tools (which we don’t create or support) to see if other XML-related fixes have resolved those.

brion 5 years

Andreas, can you link to anything specific? We’re waiting on a final check on some upload fixes; if there’s anything else left that’s Commons-specific I’ve not heard of it.

AndreasP 5 years

On the Commons Village Pump, dozens of people complain, about, quote: “one of the worst updates … ever heard of”. The Commons are virtually broken, and nothing happens, not even some news about when this all will end. On top of all this, the blog here still states “Probably a few more minor glitches to go, then we can worry about prepping the fun stuff! :)”

I understand that MediaWiki and Wikimedia server administration are mainly volunteers’ work, and we love you all for doing it, but please get away from your “fun stuff” and make the Commons work again!

Kozuch 5 years

Seems like this caused three major problems on Wikimedia Commons:
1) Uploading new version of file fails (bugzilla #20677)
2) Commonist upload tool stopped working – errors at upload
3) AWB reported not being able to log-in

Hope you fix that soon guys! ;)

AndreasP 5 years

The main bug for me is that the Commonist upload tool does not work anymore on Commons. That is a major problem for all high-volume contributors on Commons.

Roan Kattouw 5 years

Giants27 :
I’m assuming these updates are what’s causing the internal error message on every page and the one that logged me out and won’t let me log in, right?

Probably. The remaining issues will be sorted out in the morning (Pacific Time).

Giants27 5 years

I’m assuming these updates are what’s causing the internal error message on every page and the one that logged me out and won’t let me log in, right?

Roan Kattouw 5 years

Addendum from the Usability Initiative: while Babaco features will be pushed live today, they will not be enabled yet. We need to fix some more bugs, and aim to release these features as user preferences around the end of this month.

Michael 5 years

I should add while the js2 php code (scriptloader) won’t be deployed yet. We will be pushing out the javascript. This will enable us to make components like the add-media-wizard, firefogg uploads, and the new video player accessible as a gadget or opt-in feature for wider testing.

Leave a Reply

Your email address will not be published. Required fields are marked *