Not exactly a backport, but if I look correctly LTS bundles CVS plugin 1.6 which is really really old (https://github.com/jenkinsci/jenkins/blob/stable/war/pom.xml) - current is 2.8 - and has a serious problem which may affect users if they're not using CVS at all: the dreaded MailAdressResolver performance problem.

See https://issues.jenkins-ci.org/browse/JENKINS-17607 for what looks like another instance of this problem.


Kutzi

BTW: I'm a bit uneasy with taking 1.509 as the base for a LTS candidate.
I'm under the impression that still not all bugs related to the build lazy-loading have been fixed. But that's just my impression by watching what's popping up as new JIRA issues and I have no real insight of the problems.

Am 15.04.2013 10:08, schrieb Vojtech Juranek:
Hi,
as agreed on the Jenkins governance meeting [1], next LTS will be based on
1.509. I decided to backport all proposed candidates, as all seem to me valid:

JENKINS-10197 - Matrix jobs default to "locked" (and are difficult to delete)
JENKINS-15340 - Add 'Are you sure' on Reload configuration from disk
JENKINS-16845 - NullPointer in getPreviousBuild
JENKINS-17110 - Hover-over "Build Now" broken for parameterized jobs: "This
page expects a form submission"
JENKINS-17330 - FilePath.installIfNecessaryFrom routes download over remoting
channel
JENKINS-17343 - Jenkins is no more WinXP compliant : CreateSymbolicLinkW is
not available

The search was based on lts-candidate label. If you have any other proposal or
don't agree with backporting of some fixes mentioned above (currently are
backported only in repo), please discuss here.

Thanks
Vojta

[1] http://meetings.jenkins-ci.org/jenkins/2013/jenkins.2013-04-03-18.01.html
[2] 
https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line#LTSReleaseLine-Backportingprocess


--
You received this message because you are subscribed to the Google Groups "Jenkins 
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to