We already have SubPageList, SubPageList2, and SubPageList3 sitting around (SubPageList and SubPageList3 are in SVN, SubPageList is supposed to be the one more up to date then either the 2 or 3) inside MW.org and SVN. Heck it's hard to have as much of a naming mess as we've had with Dynamic Page List. So I see no reason for MobileFrontend2 to be forced to be renamed.
Can we just let John DuHart get on with writing the code so that we can have a working 1:1 replacement, put it through all the testing we need to make it the mobile code used on WMF's cluster, and then replace MobileFrontend/ with MobileFrontend2/'s code.
And for ages there was confusion about which one was actually up to date and usable. At some point everything just said "Use SubPageList, it's the up to date version". Same thing with DynamicPageList. People expect things with what appear to be version numbers. It's unfriendly, at least, to name an extension to look like a newer version.
Is it really too much to ask for it to be named something else?
- Ryan