[wildfly-dev] Call For Final Component Upgrades

[Darran Lofthouse]

On 13/04/15 14:25, Jason T. Greene wrote:
> Yes but a very short one. So far we have had nothing major on Beta, so I think it's pretty solid. It would mainly be to shake out any release errors.
>
> Ideally we wouldn't be updating all deps unless there was an actual bug we had to fix. Is there a quality concern or is it more just not jumping right to final for your component?

No real quality concern, bug fixes affected connection state so would 
just be nice for an opportunity for community to also report back.

I can tag now if you really want but also not a big deal to tag at an 
agreed date - it is a genuine candidate for release.

>
>> On Apr 13, 2015, at 7:11 AM, Darran Lofthouse <darran.lofthouse at jboss.com> wrote:
>>
>> Is there going to be a candidate release?  The reason I released a CR of
>> Remoting JMX was to try and give an opportunity for community to test
>> the reported bugs are fixed in the next WildFly CR before all are tagged
>> .Final.
>>
>>
>>> On 11/04/15 00:23, Jason Greene wrote:
>>> If you haven’t already, please send in a PR updating your component to Final status, as we hope to release 9 Final this month.
>>>
>>> Thanks!
>>> --
>>> Jason T. Greene
>>> WildFly Lead / JBoss EAP Platform Architect
>>> JBoss, a division of Red Hat
>>>
>>>
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev