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.
