I think the question you really need to ask yourself is what is driving the update.
So for example there are some changes to the SCM api in 1.568... if you want to pick up support for them then there is really only one way to do that... now I would advocate waiting for those changes to hit an LTS, i.e. wait for the post 1.565 series, but given that the LTS gets its own update center it's probably not the worst crime in the world to have updates that require a more modern core. If you are just updating *because you can* well I would say it's best to decide a threshold percentage and pick the LTS version that has that sits with that cutoff. Plugin maintainers should pick their own threshold. I'd recommend that you target a version that includes at least 50% (perhaps 80-90%) as a lower limit to the threshold... but if you want to be a dick and only maintain your plugin for the bleeding edge... well see how your users respond! In CloudBees, our proprietary plugins are agressive, i.e. we will push releases with the baseline version being the baseline version we support... OTOH where there are OSS plugins and we are pushing changes we tend to be quite conservative (e.g. I kept credentials based on 1.424 for a *very* long time, only moving off when there was both good reason - to fix some UI issues - and switching to the fix version would retain >95% of installations) as we recognise that the community has needs that may differ from our own. On 31 July 2014 00:18, 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. > -- 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.
