Hi everyone, Update on this subject:
The JEP has been created and given the JEP-231 number https://github.com/jenkinsci/jep/tree/master/jep/231 - (We will update the table listing impacted plugins in the JEP soon with the correct latest status -- latest status, checked a few minutes ago is in the PR itself for now <https://github.com/jenkinsci/jenkins/pull/5320>) What will happen when we merge the Core PR https://github.com/jenkinsci/jenkins/pull/5320? => starting with the following weekly,* the following plugins would not work anymore*: emma <https://github.com/jenkinsci/emma-plugin>, cloverphp <https://github.com/jenkinsci/cloverphp-plugin>, vs-code-metrics <https://github.com/jenkinsci/vs-code-metrics-plugin>, BlameSubversion <https://github.com/jenkinsci/BlameSubversion-plugin>, javatest-report <https://github.com/jenkinsci/javatest-report-plugin>, vss <https://github.com/jenkinsci/vss-plugin>, genexus <https://github.com/jenkinsci/genexus-plugin>, synergy <https://github.com/jenkinsci/synergy_scm-plugin>, config-rotator <https://github.com/jenkinsci/config-rotator-plugin>, harvest <https://github.com/jenkinsci/harvest-plugin>, cmvc <https://github.com/jenkinsci/cmvc-plugin> (for perspective, the emma plugin is the most installed with 3.2k installs, and then it drops quickly.) Note that we have filed a PR to fix this issue for *all* these plugins. So if anybody was to step up in the future, they could easily take ownership, merge & release the corresponding plugin. Basil has been nice enough to prepare a PR to show users that these plugins are deprecated: https://github.com/jenkins-infra/update-center2/pull/525 Hence, I think this is time for us to move forward. I think we have taken the due care needed to respect our "compatibility matters" stance <https://www.jenkins.io/project/governance/#compatibility-matters>. And given we know exactly the impact, it is reasonable to move on. *I would like to formally request we merge this PR.* If not, I'm ready to consider additional actions, but then I'd like to know which ones :). What I'm already having in the radar: * send a heads-up to the users ML * write a blog entry about this subject Anything else? Thank you! Le lun. 10 mai 2021 à 22:50, Liam Newman <bitwise...@gmail.com> a écrit : > Here's the PR submitting JEP for Digester Removal: > https://github.com/jenkinsci/jep/pull/361 > > On Wed, May 5, 2021 at 10:37 AM Oleg Nenashev <o.v.nenas...@gmail.com> > wrote: > >> Hi all. Please do not consider JEP as a huge overhead. As discussed in >> another thread, we will be working on simplifying the process for >> contributors. The process is not meant to be an obstacle, and I plan to >> keep simplifying it where possible. >> And, to everyone, please be kind. All of us share the goal to improve >> Jenkins and reduce maintenance overheads >> >> On Wednesday, May 5, 2021 at 7:13:42 PM UTC+2 Baptiste Mathus wrote: >> >>> >>> Le mer. 5 mai 2021 à 19:08, Jesse Glick <jgl...@cloudbees.com> a écrit : >>> >>>> On Tue, May 4, 2021 at 10:58 PM Oleg Nenashev <o.v.ne...@gmail.com> >>>> wrote: >>>> >>>>> What about a quick JEP? >>>>> >>>> >>>> The rule of thumb is that if you are not sure if a JEP might be >>>> needed…file a JEP. It is how we document any decision that might be >>>> controversial or require explanation or context. Certainly any >>>> deliberate compatibility break falls into this category. If your arguments >>>> for why we should do something are coherent, it should not take long to >>>> write up a few paragraphs in AsciiDoc and file it. >>>> >>> >>> Agreed. We'll do one >>> >>> >>> -- >> 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/f8066f0c-9dfe-4209-8fe8-e19bcf30b8e7n%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/f8066f0c-9dfe-4209-8fe8-e19bcf30b8e7n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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/CAA0qCNyOnh-O1o%2Bo2srtHd38G%3DQbpYA6mDS2Wt6T8M0f4ahJqw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAA0qCNyOnh-O1o%2Bo2srtHd38G%3DQbpYA6mDS2Wt6T8M0f4ahJqw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CANWgJS55S5-VsTH_r2mP%3DXdGau4abkEGEUZHyu-5Uay72YSiaw%40mail.gmail.com.
