[jboss-dev] M2 planning and timeline

[Pete Muir]

>From a CDI perspective we should:

* update to Weld 1.0.1 which should be out in time for your dates
* switch to non-flat deployment structure (Ales is working on this)
* provide proper binding for the BeanManager (this depends on the same stuff as ValidatorFactory) to java:comp/BeanManager
* ensure that EJB is using the 1.1 interceptors API

Thanks,

On 11 Dec 2009, at 22:02, 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!
> 
> -- 
> Jason T. Greene
> JBoss, a division of Red Hat
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development