Jenkins produces a new release weekly to deliver bug fixes and new features rapidly to users and plugin developers who need them.
This is called the Jenkins Long-Term Support release, or LTS. The concept is very similar to the LTS concepts in Ubuntu and our model is described below.
On the jenkins-ci.org homepage, select the "Long-Term Support Release" tab on the right.
Once you have downloaded an LTS release, proceed with installation as normal.
If you had a Latest&Greatest release running before and now have switched to LTS, you should open Manage Jenkins->Manage Plugins->Advanced and press "Check now".
Check the LTS Changelog to see what's in the latest LTS release.
See the list of issues pending backporting. In case there is a pressing issue not listed, feel free to add "lts-candidate" label to the issue so it will be considered for backporting.
Following table demonstrates release dates within the 12 week cycle. The cycle starts picking an LTS baseline at week 0. Then, there is a two week period for backporting followed by two weeks for testing the release candidate resulting in the release of 1.X.1. Backporting and rc testing is repeated two more times producing 1.X.2 and 1.X.3. This concludes cycle for a given baseline and the new one is started immediately.
See the event calendar.
We aim for no API change in LTS releases and we are backporting important fixes first. LTS release line gets its update center feed that only advertises LTS updates and not the main release line. It also gets the limited subset of plugins that work with the LTS release line. This process is adjusted as we go. Please let us know your feedback.
See Backporting toolkit for LTS for the tooling available for the developers.
Skip to end of metadata Go to start of metadata