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.
What can we do on boot time and memory footprint? What pieces can we fit
into the timeframe? Personally I don't care how small. I'm concerned if
we wait for big pieces we'll never get anywhere. If possible for each
milestone we should identify some things and get them done.
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat