<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">AFAIU, the source tree is <a href="https://github.com/jbossas/jboss-eap">jboss-eap</a>, which is not accessible for the reporter. <div>So the reporter cannot make the transition from Resolved to Closed.</div><div><br></div><div>All would be good if the reporter can verify the patch before it goes in the next EAP release, can he?<br><div><br><div><div>On Apr 17, 2013, at 12:57 PM, Heiko Braun <<a href="mailto:hbraun@redhat.com">hbraun@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I think what Darran is trying to say, is that any EAP issue needs to have an upstream issue first anyway.<div>That mean you can verify it against the community builds.</div><div><br><div><div>On Apr 17, 2013, at 12:55 PM, Thomas Diesler <<a href="mailto:thomas.diesler@jboss.com">thomas.diesler@jboss.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>The upstream process is fine.</div><div><br></div>This thread is about <a href="https://issues.jboss.org/browse/JBEAP-8">bugs</a> reported against <a href="https://issues.jboss.org/browse/JBEAP/fixforversion/12321330">EAP 6.1.0.Alpha1</a><div><br><div><div>On Apr 17, 2013, at 12:47 PM, Darran Lofthouse <<a href="mailto:darran.lofthouse@jboss.com">darran.lofthouse@jboss.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">All issues should be going upstream first anyway into what is currently marked as AS8 if that is what you mean?<br><br><br>On 17/04/13 11:16, Thomas Diesler wrote:<br><blockquote type="cite">Hi Darran,<br><br>this does not work. There is no living soul in QA that could verify my patch and guarantee that it works for the reporter. For good reason, we distinguish between Resolved/Closed - only the reporter of an issue can make the transition from Resolved to Closed.<br><br>I'd say this process is broken.<br><br>I suggest we do all work in jboss-as until an issue is not only Resolved but also Closed. Closed issues can be picked up by QA and the associated commits cherry-picked and whatever other voodoo they do in their non-public systems.<br><br>As it stands now the reporter has to wait until the next EAP release before he can know whether his issue is truly fixed. That is obviously broken, isn't it?<br><br>cheers<br>--thomas<br><br>On Apr 17, 2013, at 10:20 AM, Darran Lofthouse <<a href="mailto:darran.lofthouse@jboss.com">darran.lofthouse@jboss.com</a>> wrote:<br><br><blockquote type="cite">Thomas - to get it into EAP it must have also had a BZ which means it<br>would be verified by QE.<br><br>Regards,<br>Darran Lofthouse.<br><br><br>On 17/04/13 09:12, Thomas Diesler wrote:<br><blockquote type="cite">Folks,<br><br>when I resolve a bug for EAP, how can the reporter verify that the patch is working so that the issue can be closed?<br><br>cheers<br>--thomas<br>xxxxxxxxxxxxxxxxxxxxxxxxxxxx<br>Thomas Diesler<br>JBoss OSGi Lead<br>JBoss, a division of Red Hat<br>xxxxxxxxxxxxxxxxxxxxxxxxxxxx<br><br><br><br><br>_______________________________________________<br>jboss-as7-dev mailing list<br><a href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a><br><br></blockquote>_______________________________________________<br>jboss-as7-dev mailing list<br><a href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a><br></blockquote><br>xxxxxxxxxxxxxxxxxxxxxxxxxxxx<br>Thomas Diesler<br>JBoss OSGi Lead<br>JBoss, a division of Red Hat<br>xxxxxxxxxxxxxxxxxxxxxxxxxxxx<br><br><br><br></blockquote></blockquote></div><br><div>
<div><pre class="moz-signature" cols="72">xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx </pre><div><br></div></div><br class="Apple-interchange-newline">
</div>
<br></div></div>_______________________________________________<br>jboss-as7-dev mailing list<br><a href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a></blockquote></div><br></div></div></blockquote></div><br><div>
<div><pre class="moz-signature" cols="72">xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx </pre><div><br></div></div><br class="Apple-interchange-newline">
</div>
<br></div></div></body></html>