On 25.04.2014, at 06:06, Christopher Orr <ch...@orr.me.uk> wrote: > Stupid question: if a plugin is relying on a fix or feature that was > backported to 1.509.3, what happens to users running 1.510 which, presumably, > does not have that fix/feature?
Not a stupid question. I don't think there's a way to make this work properly (e.g. define a version requirement of "must have 1.509.3 or 1.519"). >From my POV there are a few mitigating factors though: - Only important (to LTS use) API is backported, so it should be a rare enough occurrence. - It only affects the versions between an LTS release and a weekly before the next LTS -- 6 versions in the worst case (assuming the new 12 week LTS cycle). - If you're not on LTS, chances are you're updating more frequently than once a quarter, making use of old non-LTS versions unlikely. There are fewer installations on 1.510-1.518 (missing RunAction2) than are using the latest weekly version within a week of its release. - Updating your regular release after encountering an error after a plugin installation or update (likely on startup) will fix it. - It'll take a while for your use of new API in a new plugin (in the case of the archetype) to reach users. -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
