Issues won't get fixed as quickly as they need to be in a release for two weeks
first. That said you are less likely to discover new issues - with the
exception of a new major lts version, however that has an amount of testing
which latest never has.
If you are really concerned with bugs
Probably the best approach is to use LTS, but wait a few weeks - just to
check if there are any bugs discovered (you can check community ratings
in changelog http://jenkins-ci.org/changelog-stable). Also backup
before update, and after update check if most crucial functions are
stable (do some
Hi,
we've been so far always using more recent Jenkins versions, but are
experiencing enough issues after each upgrade (especially with
plugins) that we're thinking about using LTS instead.
But on the other hand I'm worried that issues get fixed faster and get
more visibility if they're in the
Just from one plugin developer, I set my plugin up to build against the
latest LTS version, NOT the latest version of Jenkins. This means that
there have been times when changes in core have broken people who are using
my plugin with more recent versions. I prefer to keep my plugin based on
the
