On Wed, Apr 14, 2021 at 12:20 PM Daniel Beck <[email protected]> wrote:
> > Since the last time we discussed this (and I created the JEP), we added > deprecation warning support to Jenkins 2.246 and newer, which is basically > designed for such a case. This makes JEP-7 much cleaner to implement, > because we now have good ways to inform users about it. > > I'd start with a deprecation warning for ruby-runtime and all dependent > plugins pointing to the JEP or this thread (or, if you want to write it up, > a blog post), and if folks don't <s>complain</s> offer to take over > ruby-runtime maintainership in large enough numbers, we can suspend a few > weeks later, followed by core cleanup. WDYT? > > +1 from me. -- 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/CAO49JtFpo1yfG81wQYMUYp9vq3wFP%2BE40zA5cyAuZLYAQF83JQ%40mail.gmail.com.
