Legoktem, do I understand correctly that you're using current head of master for Mobile Frontend? If not, can you confirm the sha1 of MobileFrontend in question? Also, do you know the sha1 for the latest core commit in 1.21rc1? I was looking through remote branches and tags of Mediawiki core, and I can't tell what was used for creating 1.21rc1 - but if we can figure out the latest sha1 for 1.21rc1, we can probably figure out a reasonably stable point in MobileFrontend that will be compatible.

Mediawiki core development, deployment, and release packaging happens totally independently of MobileFrontend. Since we develop primarily for production on the WMF cluster, we haven't really paid much attention to ensuring MobileFrontend compatibility with specific Mediawiki releases. Maintaining specific branches (or tags) of MobileFrontend for Mediawiki release compatibility would add some overhead to our workflow. But if this is something people would find useful, perhaps there's someone who would be willing to volunteer to help out with this task?

On Sun, Apr 14, 2013 at 1:06 AM, legoktm legoktm.wikipedia@gmail.comwrote:

Hi, After upgrading my site's MediaWiki install to 1.21rc1, we noticed the MobileFrontend (at master) was throwing a fatal error. I mentioned it in #wikimedia-mobile and Ori found that it depends on a core change that was only merged recently (https://gerrit.wikimedia.org/r/#/c/49071/).

Since MobileFrontend is considered to be stable, it would be nice if there was a REL1_21 branch so that we could get the features that have been introduced since REL1_20 was branched, and that don't require 1.22. Thanks! -- Legoktm http://enwp.org/User:Legoktm

---

Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l