On Fri, Jul 3, 2015 at 10:48 AM, Ullrich Hafner <[email protected]> wrote: > I don’t see why it is helpful to make intermediate work visible to plug-in > authors, it creates a lot of unwanted noise. I think it would be sufficient > that you make code reviews within your forked repository. When the review is > successful you still can open a pull request for the original repository.
I think the presence of the `work-in-progress` label is sufficient to distinguish whether the PR author believes the work is complete or not. A repository maintainer might choose to completely ignore PRs until this label is removed. But then again they might be able to see at a glance that the approach under development is off base, and want to intervene early. Why not keep the discussion open for anyone who might want to give early feedback? -- 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/CANfRfr3dT8XAMggoH1Rd6NiACtdzfAm26pbCKGH5dq5dprbtGA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
