Move entries older than last year to changelog-old

The current changelog is *more than twice as long* as the "archive".
So it could really use some trimming. I propose to always keep the
current and previous years' entries.

Second half of the change: Remove the old entries (2012 and older).
[FIXED JENKINS-23361] Add CLI commands to add jobs to and remove jobs from views.
[maven-release-plugin] prepare release jenkins-1.567
[maven-release-plugin] prepare for next development iteration
updated changelog for release
[FIXED JENKINS-23375] Incorrect redirect after deleting a folder.
Do not mix old and new test-annotations libraries.
Corrects 9ce6b0fec3c0a0f1b9ea786865b2130a900a5886.
[JENKINS-19310] Reproduced problem in test.
Fixing the order
Integrating the fixed version of remoting
[FIXED JENKINS-19310] Provide correct links for build history inside a folder.
The basic fix is to use ${rootURL} plus full model object URLs rather than relying on ${jobBaseUrl}.
This is made trickier by the fact that the model object URLs are computed inside ProgressiveRendering.compute,
and therefore will not be correct when nondefault views are in the crumb trail unless the original request information is present.
So modifying ProgressiveRendering to preserve a copy of the original request for use during computation.
(This could probably be used to simplify parts of AsynchPeople as well.)
Also improving AbstractItem.getUrl to properly construct a URL including views even when the current page is not inside the item;
it should suffice for some ancestor of the current item (or a view thereof) to be in the ancestor list of this page.
Merge commit 'ea95434938b2111d8768528823990a78bdc58d3e'
updated changelog as a part of the release
merged back the RC branch
creating an RC branch
the trunk is toward 1.569-SNAPSHOT
Merge REMERGE_HEAD into HEAD
[JENKINS-19310] Unreproducible failure of DirectlyModifiableViewTest.failWebMethodForIllegalRequest, probably from a StackOverflowError.
	at …
	at hudson.model.View.toString(View.java:514)
	at java.text.MessageFormat.subformat(MessageFormat.java:1246)
	at java.text.MessageFormat.format(MessageFormat.java:836)
	at java.text.Format.format(Format.java:140)
	at java.text.MessageFormat.format(MessageFormat.java:812)
	at java.util.logging.Formatter.formatMessage(Formatter.java:130)
	at java.util.logging.SimpleFormatter.format(SimpleFormatter.java:63)
	at java.util.logging.StreamHandler.publish(StreamHandler.java:179)
	at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:88)
	at java.util.logging.Logger.log(Logger.java:481)
	at java.util.logging.Logger.doLog(Logger.java:503)
	at java.util.logging.Logger.log(Logger.java:567)
	at hudson.model.AbstractItem.getUrl(AbstractItem.java:423)
	at hudson.model.View.getViewUrl(View.java:510)
	at hudson.model.View.toString(View.java:514)
	at …
Reusable API documentation: <st:include page="/hudson/model/ModifiableItemGroup/_api.jelly"/>
[FIXED JENKINS-20327] When saving a list view, submit POST data with size proportional to the # of jobs selected for inclusion, not the number of options.
This can be done easily by setting json="true"; otherwise the default is to pass =false for each unselected job.
Ironically, even with this fix we are sending 2× what is needed,
since currently ListView.submit does not even check the json parameter for job names:
it only pays attention to top-level request parameters that the browser defines for selected checkboxes.
Ideally we could ask buildFormTree to ignore a given form element entirely, so as to avoid the wasted data.