--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr32TJTKwgWmM5oegVZDGCOHnxV-9EoDaO%2B71jBh6zR5-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJTHQaGTECfjPPq_kDt81YEUuWubTmyAqq7b1X%2B4YoGtMrGJDw%40mail.gmail.com.
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20170919171212.j3sjo4fawhisfieb%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
So my point about the Governance Meeting is rather a protective one, it protects both community and delegates. In some cases it will be "process just for the process" for sure. Currently the Governance Meeting is IMHO the only legitimate institution in Jenkins (no "technical steering committee", board election fun), so that's why I propose to route the approval through the governance meeting.
BR, Oleg
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/spDAr8EJm3c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/EB23042E-B108-462F-991C-845BF568A3E9%40beckweb.net.
--
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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/78ac83c8-6290-41f9-98f9-7e977ec6004b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/adc45ded-07c6-4d7d-b1ef-2cac80165796%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2b9ec3bb-96d0-46bb-8cc8-eaddbbfad3ae%40googlegroups.com.
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2z-B2cM3eL17deqnR4pawFvMR4affANhf3xaSxO5gGpg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
> On 31. Oct 2017, at 11:12, Robert Sandell <rsan...@cloudbees.com> wrote:
>
> Thoughts?
>
If it's relevant enough and not just implementation detail, it can always be added by the author even in the current format. But expecting a complete list of added/deprecated/removed APIs will just make proposing any change prohibitively cumbersome -- now you need the entire thing implemented (and not just as a prototype) before you can even ask for it to be considered. That's going to be a massive waste of time when, AFAIUI, one of the goals is making it possible to propose larger-scale changes without having every little detail mapped out (which is currently a prerequisite for having a PR discussion.
I'm pretty sure quite a bit of what's in Jesse's JEP exists there only because the implementation is basically already done. I think that's not a goal of the JEP process, and should not be.
--
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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C8261F02-D39F-4248-B8C3-549D12BC6D8E%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3jndHrP0AeytpGmyBqMu55%3DB8yihfjCrWUr%3DP9oSdS8w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMyXpRKg%2BYF0mwVt6YjQE%2BHwHpMB0iP21zD7Q-zUCcsOPw%40mail.gmail.com.