another +1 from me for #3 Especially since you won't have to do a release since its just dev tools, so there's not a lot of risk.
On Thu, Jul 11, 2019 at 10:26 AM Jeff Thompson <[email protected]> wrote: > On 7/11/19 8:22 AM, Jesse Glick wrote: > > On Thu, Jul 11, 2019 at 7:51 AM Daniel Beck <[email protected]> wrote: > >> 3. Start with PRs, but merge myself when maintainers don't. This is > basically what Oliver ended up doing when we added Jenkinsfiles to plugin > repositories.[2] > > +1 for this. An unmentioned benefit over #1 is that CI will catch > > fatal mistakes in your tool, and if you are doing some batch POM > > transformation with hundreds of cases you are going to have made a > > couple of mistakes. > > Another +1 for approach #3 from me. It's the only approach that makes > any sense as far as I can tell. > > Jeff > > -- > 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/b9a3fd6d-4f09-ac7b-c04e-e18b5c424d21%40cloudbees.com > . > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusfRwqR50dwDAfsM0KHVZb15cxcuR7OUCDzLcOJTy7s_Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
