Hey,
I'm wondering about two things:
* When will we finally drop 5.2.x support?
* Can we have isolated components in core that require 5.3?
It's been one and a half years since the PHP guys dropped support for
5.2.x. What's still keeping us from doing so? Would dropping it in 1.20
work? That'll likely be in more then half a year from now, so over 2 years
since PHP dropped support, which seems to be a very reasonable
compatibility timespan (esp if you consider 5.3 will have been available
for 3 years at that point). Personally I have not noticed the need for
5.2.x support in a while. 4 of my 6 last extensions require 5.3, and I only
had a single person complain to me about this (which was over half a year
ago IIRC). So it seems to me that people upgrading their wiki software have
5.3 already or have no problem with upgrading it.
My second question is about isolated utilities in core. With isolated I
mean that although they might be using core, core does not use them. Can we
at this point introduce such utilities that require 5.3, assuming there is
good reason to have these utilities and that they cannot be made to work
(sanely) with 5.2.x?
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
Hi all,
As some of you are probably aware, we've got a test repository converting
phase3 to git up and running on gerrit. You should be able to clone by
`git clone https://gerrit.wikimedia.org/r/p/test/mediawiki/core.git`
Couple of caveats (things I'm gonna try and fix):
* Permissions aren't sorted yet, so it's only supporting anonymous clones,
no pushing yet.
* The revision graph is crazy. svn:mergeinfo is unreliable and we're pretty
much unable to build a cohesive history without a *lot* of manual labor. Right
now I'm thinking of just dropping the mergeinfo so the branches look like linear
graphs cherry picking from master. Not perfect, but less annoying than now.
But yay progress! Clone it. Try it out, see what works (and what doesn't).
I'll try to get the permissions sorted later today so we can go ahead and
try some test pushes (and merges).
Things we still need to do:
* Make a git-setup like we've done for the other git repos. This will setup your
environment/hooks/etc for you.
* Figure out our WMF branching/deployment strategy, since we're very SVN-
centric right now with this.
Thanks for any input, guys.
-Chad
If you're looking for an extension name, here are some possibilities:
MobileAccess
MobileDisplay
MobileView
Mobilize (a little play on words there)
-Yaron
Greetings,
The Wikimedia Foundation is planning to upgrade MediaWiki, the
software powering Wikipedia and its sister sites, to its latest
version.
The upgrade will happen in several stages over the month, starting this week.
You can still help to test it before it is enabled, to avoid
disruption and breakage.
More information:
* Announcement on the Wikimedia blog:
https://blog.wikimedia.org/2012/02/11/mediawiki-1-19-deployment/
* The announcement in other languages:
https://www.mediawiki.org/wiki/MediaWiki_1.19/Deployment_announcement
Thank you for your understanding.
--
Guillaume Paumier
Technical Communications Manager — Wikimedia Foundation
Hi everyone,
After Niklas mentioned in another thread that the i18n team was
effectively ignoring the code slush, I decided to do some spot
checking to see what couldn't wait. What I saw was a lot of backwards
compatibility breakage that's going to make releasing 1.19 and the
eventual 1.20 release a lot harder, and make life generally miserable
for third party users of MediaWiki that just want to stay on top of
security releases and maybe want to install a new extension or two,
but have extensions that they can't afford the dev resources to
update. I've been there myself, and it sucks.
At a minimum, we need to start marking backwards-compatibility
breaking changes. So, I've created the "backcompat" keyword, and
started the task of marking these. I'd like help in marking these
things, since I suspect we've got a lot of work before we can release
a 1.19 tarball.
Here's the list so far:
http://www.mediawiki.org/wiki/Special:Code/MediaWiki/tag/backcompat
It's hard enough to make things work. Expending effort trying to make
things *not* work is bound to be more successful than anyone is
banking on. Please stop this.
Thanks
Rob