I'm in for this proposal. We need a way to clean up the ecosystem to be able to progress easily without investing too much on things that are not used.
We can discuss and polish the details, but the aim remains the same. Thank you Oleg for triggering the discussion. On Tue, May 4, 2021 at 7:08 PM Oleg Nenashev <[email protected]> wrote: > I tentatively put the topic to the tomorrow's governance meeting agenda: > https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.1gtco63t6ztr > We will discuss it if there are the stakeholders from this thread and > enough time left. > > > > On Monday, May 3, 2021 at 3:25:32 PM UTC+2 Jesse Glick wrote: > >> On Mon, May 3, 2021 at 3:46 AM Daniel Beck <[email protected]> wrote: >> >>> Something more extensible, with version ranges like we do for security >>> warnings could help here: >>> "This plugin is likely to break the UI once you update Jenkins to >>> 2.277.x" and "no fix is available" or "update to version X or newer". >>> >> >> FYI https://issues.jenkins.io/browse/JENKINS-49651 >> > -- > 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/9c82d2f8-4f8a-4cf2-b1a1-ea8247c8e530n%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/9c82d2f8-4f8a-4cf2-b1a1-ea8247c8e530n%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CADN1OJ31%3D_fRNMSxSktSBr%3DzmfYEW6QgSbk63L0MQUmvORbNTw%40mail.gmail.com.
