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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Jason T. Greene
JBoss, a division of Red Hat