Daniel, >From that link:
> This is not to say we don’t ever remove anything, but we do it very > carefully. > We are being careful. I think creating a JEP, even a mostly retrospective one, is worth doing. If nothing else we should do so because of concerns like those voiced by Daniel. I will take that task on myself if needed. -L. On Wed, May 5, 2021 at 5:14 AM Daniel Beck <m...@beckweb.net> wrote: > > > > On 5. May 2021, at 09:41, Manuel Ramón León Jiménez < > manuelramonleonjime...@gmail.com> wrote: > > > > I'm against a JEP for Digester removal. It doesn't need it IMO. I'm in > for anything to avoid us dealing with the same problems in the future. We > need to modernize Jenkins in many aspects and those old / unmaintained > plugins are an obstacle and a waste of effort. > > Time to delete > https://www.jenkins.io/project/governance/#compatibility-matters then, > because looking at this thread, compatibility clearly doesn't matter > anymore? > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/B214EACA-57A8-4EB4-9FFA-C59B2F0D9D89%40beckweb.net > . > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAA0qCNwD%3DMMh5i%2BjeEte6CxRqQ%3DcCVEZqmNMxtPcgC8JUJ_0vA%40mail.gmail.com.
