[jbosstools-dev] Bug in Forge/JBDS 8.1.0.CR1, do we really need a respin?

Alexey Kazakov akazakov at exadel.com
Wed Mar 18 16:44:28 EDT 2015


BTW what is QE status for CR1? I don't see any other issues reported in 
JIRA. How much time do you need to finish CR1 testing?


On 03/18/2015 01:23 PM, Len DiMaggio wrote:
> Would we want to pull in the fix and try to release CR1 at be end of 
> the planned QE test cycle? We've already missed the 18th.
>
> --Len
>
>
> (Sent from my iPhone)
>
>
>
> On Mar 18, 2015, at 1:52 PM, Alexey Kazakov <akazakov at exadel.com 
> <mailto:akazakov at exadel.com>> wrote:
>
>> Hi,
>>
>> We have an issue in the latest Forge 2.15.1.Final (upgraded in JBDS 
>> 8.1.0.CR1) - https://issues.jboss.org/browse/JBIDE-19468
>> It prevents creating a forge addon. The workaround described in the JIRA.
>> The issue itself doesn't look like a blocker for JBDS 8.1 to me. 
>> However, George Gastaldi said that they are going to release a fixed 
>> Forge 2.15.2 today or tomorrow and *IF* we can do a respin for the 
>> forge component (with upgraded forge) *with no big cost* maybe it's 
>> worth doing.
>>
>> WDYT?
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150318/e3cd8b6f/attachment.html 


More information about the jbosstools-dev mailing list