We decided to base the upcoming LTS line on 1.636 in the last meeting on Dec 9. 1.637 introduced two regressions (JENKINS-31458 and JENKINS-31518), that were only resolved in 1.639 and 1.640, so we didn't consider those to be great choices. 1.640 in turn introduced another bug, JENKINS-31954, which was only fixed in the then-unreleased 1.642.
It has been three weeks since the meeting, and we've had very positive feedback for the last two releases, Jenkins 1.642 and 1.643.[1] There have been no notable further regressions reported in JIRA either. Since we've skipped the Dec 23 meeting, the LTS schedule has been moved two weeks: The next LTS release is planned for Jan 20, with backporting finished Jan 6 (so far, it hasn't really started[2]). Given all of the above, it may be feasible to advance the version chosen for the LTS baseline to 1.642 or 1.643, rather than stick to the previous choice made necessary by the regressions in later releases, while keeping the expected schedule. WDYT? 1: http://jenkins-ci.org/changelog (click 'Community ratings') 2: https://github.com/jenkinsci/jenkins/commits/stable-1.636 -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ADCD1759-9515-4361-A1C3-4B8F6DB4BF0D%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
