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

[Alexey Kazakov]

We go with #1.
We release CR1 today with the current/"broken" forge. Fix/upgrade Forge 
in 4.2.x. Include the updated forge component in the upcoming GA release.

On 03/19/2015 06:19 AM, Nick Boldt wrote:
> So... the plan for JBIDE-19468 is to do one of these:
>
> 1. fix it ASAP and get it in front of QE after next Thursday's GA code 
> freeze (no change to schedule)
>
>  -- OR --
>
> 2. fix it today and postpone CR1 by a couple days (change schedule)
>
>  -- OR --
>
> 3. reject the release of CR1 entirely (change schedule by keeping CR1 
> internal), fix it ASAP, and simply release GA on schedule
>
> What's the best plan here? I can accommodate any of the above.
>
> On 03/18/2015 08:29 PM, Len DiMaggio wrote:
>> The full test cycle will wrap up on the 26th - on schedule.
>>
>> The pre-can-we-release-the-CR1-build-ASAP testing was scheduled for 2
>> days - so we will finish that on March 19.
>>
>> --Len
>>
>>
>> (Sent from my iPhone)
>>
>>
>>
>> On Mar 18, 2015, at 4:44 PM, Alexey Kazakov <akazakov at exadel.com
>> <mailto:akazakov at exadel.com>> wrote:
>>
>>> 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
>>>
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>