On Thu, May 30, 2019 at 3:08 AM Francisco Javier Fernandez <[email protected]> wrote: > That issue, although it's in progress seems to be paused since 8 months ago.
I adjusted status accordingly. (Makes no sense for an issue with no *Assignee* to be *In Progress* anyway!) > Maybe what Daniel says makes sense: disable or remove it and create a new > plugin, but not a detached one. Basically the same thing, just comes down to whether after publishing the newly split plugin you decide to include it in core’s list of detached plugins or not. I agree that there is not a compelling compatibility argument to do so. -- 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/CANfRfr1k61q%3DMF0TKT1tgLLgZLK2e8AtuFi5ng0U8H%2BkwFkNkQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
