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 latest LTS because I feel its more stable.
</twocents> slide On Mon, Dec 9, 2013 at 4:01 PM, Klaus Schniedergers <[email protected] > wrote: > 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 newest version. > > What are your experiences with Jenkins LTS versions? Are these more > stable in the long run? Do they get enough attention to have important > fixes being backported? Are plugins supporting LTS well? > > Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Website: http://earl-of-code.com -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
