Proposal talk:Tech transparency: What are we running?

From Strategic Planning

This is exactly one of the reasons we started using a deployment branch; the exact software we're running right now is in the wmf-deployment branch in our SVN; you can see updates to it in CodeReview.

Now that we're past the giant branch merges (js2, new-upload, and maintenance-work) we should be on a more regular update schedule, which will also mean that the changes from major update to major update will be smaller and clearer; the tech blog will be our key release outlet for such announcements (which are usually replicated also on wikitech-l, identica/twitter, and at least a couple Village Pumps). --Brion VIBBER 21:49, 21 September 2009 (UTC)Reply[reply]

Note that making the deployment schedule explicit and visible could be a huge help here. --Brion VIBBER 22:04, 21 September 2009 (UTC)Reply[reply]
This is great news, but I am still missing a feature to show whether a certain revision has been implemented. Right now this is a huge problem for Commons as the last software update broke reuploading over existing files and users keep asking whether this is fixed. Unfortunately we don't have a way to tell whether the fix is already live or not, it's basically a guessing game. Regards, --ChrisiPK 22:05, 21 September 2009 (UTC)Reply[reply]
Yeah, that was pretty frustrating on Commons -- I had trouble with a number of files I was trying to update, with no clear place to go for answers.
Development is not really my area, but I'm curious -- is there a Mediawiki developers' blog? Could that be a useful tool to meet this need? -Peteforsyth 21:39, 1 October 2009 (UTC)Reply[reply]