On Thu, Aug 29, 2019 at 5:42 AM Oleg Nenashev <[email protected]> wrote: > Bump the version, potentially break CI for plugins (Jesse's PR) > Pin the version, allow overriding it (Baptiste's PR) > Reject both PRs, keep status quo and old Jenkins core until a > plugin-repo-side suggestion is implemented by somebody
I would add a fourth option: deprecate `recommendedConfigurations` and advise plugin authors to use an explicit list of configurations (updating the latest `jenkinsVersion` on their own schedule) until we have the time to create a more easily maintained system. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0HVzA10n7KSv%3DqeJN8QhncocQx%2BNSY_yut2VfGVvesjQ%40mail.gmail.com.
