This feature flag was added to comply with WMF's schema change policy.
It is no longer needed now that the feature is enabled on WMF sites.
External MW installations will run update.php or manually do DB updates
as required before upgrading MW.
Bug: T162517
Change-Id: I5b532d79fd1e8b178490cf2617499ae62967de2c
Changes to master that are going to be immediately backported to
REL1_29 before release should write changes to HISTORY directly.
Change-Id: Ia3e02293b13406e7a4741ef14897dd83bca98d46
We bumped to version 1.28 in mediawiki recently but seems we forgot to do
it in PHPVersionCheck.php.
Change-Id: I2a455669b68225fd9d6772c8482559c220d433b5
Copy in release notes for last releases:
1.26.2: Iae3ab6fe60b348abf6f2723b2601bd64fb3261ba
1.25.5: I995da41b703eab7b6435ab6745d8513b53c533f5
1.24.6: I05d2c3e6ed8527ba1933558f9636a3beb2d6bd80
1.23.13: I5080cf9fa699c59ee5d2bb2ae9bbbb09fa262e41
Remove Compatibility and Upgrading section from 1.25, previous releases
does not include this section, too.
Update header structure:
- Added missing header
- Increase h2 to h3 when needed
- Decrease h2 to h1 when needed
Change-Id: I37a1134c539bdcb728816fe9825c56de18878d03
All unused:
* $wgProfileCallTree
* $wgProfilePerHost
* $wgUDPProfilerHost
* $wgUDPProfilerPort
* $wgUDPProfilerFormatString
* $wgStatsMethod
* $wgAggregateStatsID
* $wgStatsFormatString
The only one still used was $wgProfilePerHost.
Also move release notes for ade945b97a from HISTORY to RELEASE-NOTES (Oops!)
Change-Id: Ia0280d23674ace1ac33aa561b06ee73cab865b29
These scripts interact with keys that used to be set by ParserCache.php.
However this hasn't been the case for a long time now. They use wfIncrStats(),
which is configured by $wgStatsdServer.
Change-Id: Id6a62aec57801085ed684af9362a96eca0914e92
Used the REL1_23 version of that file, and moved the note added in
5e48ad2e78 to RELEASE-NOTES-1.24, where it belongs.
Change-Id: Id5f4726152fc2f4c90117762f6dc4904f5fa9f94
Added in HISTORY (section API changes):
* (bug 35993) Deprecated gettoken parameter - support will be removed in 1.22.
This is a follow-up for change I369ddc74.
Change-Id: Ie78e1061353725793dbba2876037fb32cb9035a8
* The one in history isn't final yet, which makes maintenance
harder as it would have to be synced between 2 different file
names across 2 different branches.
* For backport commits its easier if the 1.20 file is still in
master so that they can be written together with the commit
(and so that the history is in master as well), as opposed to
merging it in master without notes and then adding them later
on in the (amended) merge version.
Change-Id: I3fa4b88a5845a51e83221d78facaba1ddb3b1acb
