HornetQ 2.4.0 will probably still be alpha by then. We are working on fixing the TCK
before we can call it Beta.
As long as you are ok with having a component called Alpha on your Beta...
On Jul 19, 2013, at 4:35 PM, Jason Greene <jason.greene(a)redhat.com> wrote:
The plan is to do a beta, but we will only call it beta if we are
happy with what was delivered, and want to raise interest on the release. Alternatively if
we feel the milestone isn't quite ready, we will release it as Alpha4, and have the
next release be the first beta.
On Jul 19, 2013, at 1:42 PM, Cheng Fang <cfang(a)redhat.com> wrote:
> According to
>
http://lists.jboss.org/pipermail/wildfly-dev/2013-May/000062.html ,
> Beta1 comes after Alpha3, which we just successfully released. Now
> WildFly is on Alpha4.
>
> So is Alpha4 an additional release added, or in lieu of Beta1? How will
> it impact subsequent milestone releases?
>
> Thanks,
> Cheng
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev