Last modified: 2014-11-14 08:15:37 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 42723 - Update HISTORY with point release changes
Update HISTORY with point release changes
Product: MediaWiki
Classification: Unclassified
Documentation (Other open bugs)
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: easy
Depends on:
Blocks: documentation
  Show dependency treegraph
Reported: 2012-12-05 13:04 UTC by Sam Reed (reedy)
Modified: 2014-11-14 08:15 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Sam Reed (reedy) 2012-12-05 13:04:12 UTC
For the last few sets of point releases, the change logs (in their respective branches) need bringing into the core master HISTORY file
Comment 1 Sam Reed (reedy) 2013-09-08 21:52:08 UTC
To answer comments on #mediawiki.

This is indeed easy. If there are point release (etc) for versions of MediaWiki that aren't actually in HISTORY (ie they're in REL1_20's RELEASE-NOTES, but not in HISTORY of master, they need bringing in)

Copy, paste, some common sense => easy
Comment 2 Gerrit Notification Bot 2014-11-13 20:51:38 UTC
Change 173093 had a related patch set uploaded by Ckoerner:
added updated version history from 1.19.2 to 1.22.13 (bug 42723)
Comment 3 Gerrit Notification Bot 2014-11-14 08:15:37 UTC
Change 173093 had a related patch set uploaded by Nemo bis:
Added updated version history from 1.19.2 to 1.22.13

Note You need to log in before you can comment on or make changes to this bug.