For email-ext, I generally move it to the latest LTS and run all the tests and then do a release after I've discovered all the things that changed in core that I need to update for :-)
I am not sure there is a good way to assess that yourself, you could release a beta version to the update center and ask people to test it. Other than that, I don't know of a good way. On Wed, Jul 30, 2014 at 4:18 PM, Mark Waite <[email protected]> wrote: > The git plugin and the git-client plugin are both currently based on the > 1.509 release. That was first released 15 months ago. > > Since those two plugins seem to be used in approximately half the reported > Jenkins installations, they should support multiple releases. How long a > "back level support" is reasonable? > > How would I assess the risk to users of switching the base release from > 1.509 to 1.532? > > -- > Thanks! > Mark Waite > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- Website: http://earl-of-code.com -- 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]. For more options, visit https://groups.google.com/d/optout.
