<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thank for confirming this Fernando. Earlier in the thread I said <div><br></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><i>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?</i></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><i><br></i></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"></blockquote>What would you say about that?<div><br></div><div>cheers</div><div>--thomas<br><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div> </div></blockquote><div><div><div>On Apr 17, 2013, at 3:10 PM, Fernando Nasser <<a href="mailto:fnasser@redhat.com">fnasser@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Right, jboss-eap/6.x is the AS 7.2.x series that only exists for EAP 6 purposes.<br><br>The jboss-as/7.1 died at 7.1.3 by EAP 6.0.1 time, and the jboss-as/master moved to AS8 and it is already considerably different.<br><br><br><br><blockquote type="cite"><br>… and where is upstream for EAP-6.x ?<br><br><br>I think it is jboss-eap/6.x , and not jboss-as/7.1<br><br><br><br><br>On Apr 17, 2013, at 1:04 PM, Heiko Braun < <a href="mailto:hbraun@redhat.com">hbraun@redhat.com</a> > wrote:<br><br><br><br><br><br><br><br><br>If the patch needs to be upstream first, the upstream build can be<br>used to verified it, no?<br><br><br><br><br><br><br>On Apr 17, 2013, at 1:02 PM, Thomas Diesler <<br><a href="mailto:thomas.diesler@jboss.com">thomas.diesler@jboss.com</a> > wrote:<br><br><br>All would be good if the reporter can verify the patch before it goes<br>in the next EAP release, can he?<br><br><br><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>https://lists.jboss.org/mailman/listinfo/jboss-as7-dev<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></body></html>