An integration freeze of Feb 1 for most libraries is fine, but to ensure
we actually ship the AS in Feb I think we should shoot for an earlier
cutoff for core stuff like MC/VDF/VFS/ProfileService. I'd be a lot more
comfortable with January 15 for those. Even earlier if possible.
Ales, you mentioned on another thread today that you thought MC 2.2
would be ready in a week or so. Could you commit to a January 8 date for
getting it into AS trunk?
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