They're going to be useless in Git. Need to come up with a new versioning scheme.
Version: unspecified
Severity: normal
Description
Description
Details
Details
- Reference
- bz33287
Related Gerrit Patches:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Yurik | T37885 Sane output for http://www.mediawiki.org/w/api.php?version needed with git | |||
| Resolved | Anomie | T35287 Get rid of svn keywords in API files |
Event Timeline
There are a very large number of changes, so older changes are hidden. Show Older Changes
Comment Actions
Please refrain from any self-merge not before checking with an extension developer whether 1.19/1.20 compatibility is broken or not.
PleaseStand 5:36 PM
In 1.20 and older, ApiBase::getVersion() was an abstract method, so this change would break compatibility with those MW versions.
Comment Actions
Extensions SemanticWatchlist, SemanticForms and SemanticResultFormats needs reapply when min version is moved up to 1.21 for each extension.
Extension SemanticMediaWiki is on hold for the same reason.
Comment Actions
There were not any self-merges of any of the primary patches here (Umherirrender did self-merge reverts of some of the patches he merged). Since self-merging is a rather serious accusation, please refrain from using the term incorrectly. Thanks.
Comment Actions
Since self-merging is a rather serious accusation, please refrain from using the term incorrectly. Thanks.
Those merges have been made without consent of any of the extension developers therefore are categorized as self-merges. Please don't make the assumption that just because you can +2 you can do this without contacting a maintainer of those extensions.
Thanks.
Comment Actions
No, a self-merge is when you merge your own change. Not just when someone who isn't you merges a change to your extension.
Comment Actions
Change 184672 abandoned by Jeroen De Dauw:
Remove long-deprecated ApiBase::getVersion()
Reason:
Our repo is at https://github.com/SemanticMediaWiki/SemanticMediaWiki
Do not submit non-i18n changes on Gerrit.
Comment Actions
Except for SemanticWhatever this is done, SemanticWhatever is maintaining compatibility with ancient versions of MW in their core branch so it can't be fixed, and the SemanticWhatever devs don't even want patches in Gerrit. So let's call this Resolved.