Re: [jboss-as7-dev] How to verify a patches for non-public AS
Thank for confirming this Fernando. Earlier in the thread I said
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.
I'd say this process is broken.
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.
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?
What would you say about that?
cheers
--thomas
On Apr 17, 2013, at 3:10 PM, Fernando Nasser <fnasser(a)redhat.com> wrote:
Right, jboss-eap/6.x is the AS 7.2.x series that only exists for
EAP 6 purposes.
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.
>
> … and where is upstream for EAP-6.x ?
>
>
> I think it is jboss-eap/6.x , and not jboss-as/7.1
>
>
>
>
> On Apr 17, 2013, at 1:04 PM, Heiko Braun < hbraun(a)redhat.com > wrote:
>
>
>
>
>
>
>
>
> If the patch needs to be upstream first, the upstream build can be
> used to verified it, no?
>
>
>
>
>
>
> On Apr 17, 2013, at 1:02 PM, Thomas Diesler <
> thomas.diesler(a)jboss.com > wrote:
>
>
> All would be good if the reporter can verify the patch before it goes
> in the next EAP release, can he?
>
>
>
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thomas Diesler
> JBoss OSGi Lead
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Attachments:
- attachment.html (text/html — 3.2 KB)