This extension has moved. If this is still an issue, then please open a ticket at https://github.com/JeroenDeDauw/Validator/issues - thanks!

At this point this is not really an issue in practice given that most extensions have moved to extension.json, or no longer autoload entry points in composer.json, so using an explicit $GLOBALS isn't needed.

That is no more needed, ton of things have changed since the task got filled. Notably:

@hashar any idea what the state of this one is?

I got another case.

No feedback. Assuming this got fixed by the patches.
If not, please reopen or report a new task.

Both patches got merged ages ago.
Is this still an issue? Or can this be closed as resolved?

Change 227238 abandoned by Paladox:
Fix using $GLOBALS in database updater

Change 265179 merged by jenkins-bot:
Remove dependancy on DataValues as it's been removed from Gerrit...

Change 265179 had a related patch set uploaded (by JanZerebecki):
Remove dependancy on DataValues as it's been removed from Gerrit...

With "Patch to extensions wmf branches" is B the one under test? Then A will AFAIK correctly be at what the submodule says. Only B will possibly be ahead of its submodule (more ahead than the patch under test), but that is what we want. Which wmf core branch(es) will you use here? The same extension wmf branch may be used in more than one core wmf branch. Maybe if the same tests were ran again when updating the submodule in core wmf branches we would only need to test with one core branch.

But I thought that mediawiki core is updated when a patch is merged to an extension.

The linked patch doesn't address this bug, and I remain unconvinced that this should be fixed based on the ugliness/hackiness of the code, and when migrating to extension.json will resolve the issue. or doing what Translate does and not autoload via composer.

If the extension uses the extension.json file the web updater will work for it.

The idea of mediawiki-extensions-* jobs was to test ahead of time what the result of wmf branch will be. As early as when a patch is proposed to master branches.

In T113731#1686310, @mmodell wrote:

CI should just check out all the submodules by following the submodule sha1 references in the core branch, then it wouldn't matter how the branches are named, ci would do the right thing by simply letting git do the right thing.

Translate is still installable via composer. It just wont automatically load for MediaWiki.

Does translate still support composer since it doesn't use $GLOBALS any more. If so composer should be kept as it is and convert to using extension.jspn and keeping the main php as back compat.

Translate is no longer using $GLOBALS so I removed it from the tags. Expected to be released in MLEB 2015.10.