[jboss-dev] M2 planning and timeline

[Brian Stansberry]

Are we going to do a new release of the org.jboss.mx artifacts (AS is 
currently using 6.0.0.Beta1)?  6.0.0.Beta1 is missing 
https://jira.jboss.org/jira/browse/JBAS-6945. This is the cause of the 5 
testsuite failures discussed at 
https://jira.jboss.org/jira/browse/JBAS-7606.

There are a lot more differences between trunk and 6.0.0.Beta1 than 
JBAS-6945. I have a full diff if anyone wants me to send it to them. 
(Bit big to send to the list.)

On 12/11/2009 04:02 PM, Jason T. Greene wrote:
> Hi Guys,
>
> Now that M1 is out lets talk about M2 and what can make the release. The
> tentative release plan we have talked about is a integration freeze on
> Feb 1, with an eventual freeze in late Feb. However, before we get more
> absolute dates we really need to nail down on what we aim to deliver in
> that time frame.
>
>   From an EE perspective it seems the following are close enough that
> they could make such a schedule:
>
> Full Servlet 3
> Full JPA 2
> Some EJB 3.1 capabilities (but which ones?)
>
> Other updates that have been proposed:
> - Inclusion of Remoting 3 (but full service porting to occur later)
> - Inclusion of HornetQ (need to understand more about the effort to migrate)
>
> If your project is on the above list, let me know what your schedule is
> like, and if it can fit the above timeline.
>
> If your project update is not on the list, but would like to have it
> included, and the above timeframe is workable, let me know.
>
> Thanks!
>


-- 
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat