On Fri, Mar 23, 2018 at 8:11 AM, Carlos Sanchez <car...@apache.org> wrote: > "all 'significant changes' to a JEP should be > completed before it is Accepted" looks like a requirement that may hinder > innovation and experimentation on areas that are not clear from the start.
To play devil’s advocate (I do not have strong feelings about this), we should just make it comfortable enough to file follow-up JEPs that this is normal practice. A JEP should stay as a Draft until there is a clearly working implementation released. Once Accepted, there should no eyebrows raised by filing another (initially Draft) JEP like “2018 refreshes to JEP-234 in light of mistakes made”. That can discuss any compatibility issues that might affect early adopters of the original version. -- 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/CANfRfr0F9z4sXKfZOGU%3D2vtveBt%2BdqReBy%2B4o5tpcwmNTKYEOQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
