[jboss-as7-dev] How to verify a patches for non-public AS

[Jason Greene]

Can we please take this internal Red Hat process discussion off the community list? I am sure that 99% of our external subscribers would rather not get spam about this kind of thing, and much rather see technical topics :)

On Apr 17, 2013, at 9:25 AM, Thomas Diesler <thomas.diesler at gmail.com> wrote:

> Again, how can a reporter verify a patch that I cannot apply to the jboss-as code base? 
> It's a patch for the OSGi 4.2 Framework that nowadays only exists in jboss-eap, AFAIK.  
> 
> On Apr 17, 2013, at 4:22 PM, Brian Stansberry <brian.stansberry at redhat.com> wrote:
> 
>> Any fix in EAP has a bugzilla behind it, and QE verifies all bugzillas before they are closed.
>> 
>> The fix should be fixed in the upstream AS7 project at the same time or earlier, so the reporter can verify there. Granted, there can be relevant differences between upstream and EAP. For the reporter to verify against EAP itself they'll need to wait for the EAP beta or whatever that contains the fix.
>> 
>> On 4/17/13 3:07 AM, Thomas Diesler wrote:
>>> Folks,
>>> 
>>> when I resolve a bug for non-public AS, how can the reporter verify that the patch is working so that the issue can be closed?
>>> 
>>> cheers
>>> --thomas
>>> 
>> 
>> 
>> -- 
>> Brian Stansberry
>> Principal Software Engineer
>> JBoss by Red Hat
> 

--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat