<div dir="ltr">I agree.<div><br></div><div>Separating things also means that the eventual fix PR probably isn't going to have the test. So it can either get merged without the test (bad) or the people doing merging are misusing their time coordinating combined testing of two PRs.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 17, 2018 at 8:11 PM, Stuart Douglas <span dir="ltr"><<a href="mailto:stuart.w.douglas@gmail.com" target="_blank">stuart.w.douglas@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Everyone,<div><br></div><div>Historically we have been ok with pull requests being submitted that add tests for things that are not yet complete.</div><div><br></div><div>In practice this has been kinda problematic for reviewers, as these pull requests can hang around for a long time, and this ends up wasting a lot of reviewer time as we have to continually check the status of the PR. You basically end up with multiple reviewers continually polling the issue to check if it is ready, instead of a single person just submitting it when it is complete.</div><div><br></div><div>I think that there is no real benefit to having the tests as a seperate PR that gets opened before the fix. Instead I propose that tests that do not pass yet are linked/co-ordinated under the relevant JIRA, and when the fix is submitted the tests can be submitted as part of the same PR.</div><div><br></div><div>Does anyone have any objections to this?</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Stuart</div></font></span></div>
<br>______________________________<wbr>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Brian Stansberry<div>Manager, Senior Principal Software Engineer</div><div>Red Hat</div></div></div>
</div>