<div dir="auto">I'm ok with that rule except for one case when the pr is done before the version bump has been merged then the Jenkins build will fail because of the baseline check so maybe we need to update the pr Jenkins build <div dir="auto"><br></div><div dir="auto">Jeff</div></div><div class="gmail_extra"><br><div class="gmail_quote">Le 9 mai 2017 23:10, "Mickael Istria" <<a href="mailto:mistria@redhat.com">mistria@redhat.com</a>> a écrit :<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>FYI, not merging the broken patches is the policy followed by most Eclipse.org projects and overall, none of this project has complained from a reduced productivity; on the contrary, catching and fixing issues immediately on the right context has improved quality and reduced the necessary amount of quick fix patches (which are actually quite time consuming and stressful for their low added-value).<br></div>So I think if it works for Eclipse.org projects, it can work for JBoss Tools.<br><br></div>Cheers,<br></div>Mickael<br></div>
<br>______________________________<wbr>_________________<br>
jbosstools-dev mailing list<br>
<a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/jbosstools-<wbr>dev</a><br></blockquote></div></div>