[jboss-dev] One Week Until CR1 Component Freeze!

[Alexey Loubyansky]

2.0.1.CR2 has not shown new regressions and I've released the GA.

There are two failing tests in the AS testsuite but looking at the 
causes they should have been failing since 2.0.1.CR1.

org.jboss.test.xml.SingletonSchemaBindingResolverUnitTestCase.unknown - 
needs to update to the new default schema resolver impl.

org.jboss.test.xml.mbeanserver.XMBean2UnitTestCase.testJavaBeanSchemaInitializerInterceptor 
- missing correct propOrder.

I'll fix both of them.

Ales Justin wrote:
> So, what's the status on this.
> Do we need new MC GA releases or are we happy with the old one's?
> 
> The old one's have not been used for a while now.
> Currently we use Ms, which are basically trunk snapshots.
> 
> Scott, what's the current Managed version?
> 
> What's the exact freeze date? Tomorrow or Monday?
> 
> Alexey Loubyansky wrote:
>> Yes, the purpose of CR1 was for testing. I haven't heard of any issue 
>> except for setting -Dxb.builder.useUnorderedSequence for the 
>> testsuite. So, no problem with doing GA.
>>
>> I'll do maybe one more thing for the binder: if a Java type is bound 
>> to a sequence and doesn't use @XmlType.propOrder then the binding will 
>> fail with an exception. We've seen how missed propOrder can cause 
>> deployment errors in 5.0.0.GA in some environments. So, really if you 
>> bind to a sequence and don't use propOrder your project/product may 
>> fail on a different JVM. I'll make a config option for that as well.
>>
>> Jason T. Greene wrote:
>>> Good question. Currently we have CR versions, as opposed to the final 
>>> GA, for those updates. Alexey, was this just to give time for 
>>> catching regressions? Could we move to a GA in a week's time?
>>>
>>> Ales Justin wrote:
>>>> I don't see XB update on this list.
>>>> So it's probably not going in?
>>>>
>>>> But if we want to include it,
>>>> then we need the whole MC update as well.
>>>>
>>>> Jason T. Greene wrote:
>>>>> We still have 11 updates, and only one week is left until freeze. 
>>>>> We also only have a week for catching regressions, so we should 
>>>>> avoid including anything at the last minute. Therefore, let me know 
>>>>> if any of these should *not* be moved to 5.1.0.GA (except for 
>>>>> jboss-managed, which has to be included), and if so, when they will 
>>>>> be included.
>>>>>
>>>>> https://jira.jboss.org/jira/browse/JBAS-6552
>>>>>
>>>>> JBAS-6691 Upgrade JGroups to 2.6.10             Brian Stansberry
>>>>> JBAS-6661 Upgrade Web Beans to 1.0.0.PREVIEW    Pete Muir
>>>>> JBAS-6636 Upgrade JBoss Cache to 3.1.0.GA       Brian Stansberry
>>>>> JBAS-6635 Upgrade JAXB to 2.1.9.patch           Shelly McGowan
>>>>> JBAS-6634 Upgrade JBossWS Native to 3.1.1.GA    Alessio Soldano
>>>>> JBAS-6633 Upgrade jboss-ha-server to 1.2.0.GA   Paul Ferraro
>>>>> JBAS-6621 Update jboss-managed to 2.1.0.GA      Scott M Stark
>>>>> JBAS-6564 Include JBoss Negotiation 2.0.3.SP1   Darran Lofthouse
>>>>> JBAS-6364 Upgrade apache-beanutils to 1.8.0     David Walluck
>>>>> JBAS-6052 Upgrade jboss-profiler-jvmti to final Clebert Suconic
>>>>> JBAS-6652 Upgrade AOP to 2.1.0.GA               Kabir Khan
>>>>>
>>>>>
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>
>>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development