[jboss-dev] M2 planning and timeline

David M. Lloyd david.lloyd at redhat.com
Fri Dec 11 17:42:27 EST 2009

On 12/11/2009 04:14 PM, Brian Stansberry wrote:
> 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)
> What does that mean? There'd be parallel connectors for a while? (Not
> objecting, just realize I don't know.)

Yes, parallel connectors.  It means that at a minimum, Remoting 3 would be 
integrated with an XML schema to create basic endpoint and service 
deployments, but it wouldn't necessarily relate to any existing services 
using Remoting 2 in any way.

The idea is that we could then start moving stuff over to use Remoting 3 
gradually.  Though that might not really be possible in practice.  Just 
seems like a way to make the migration bite-sized.


More information about the jboss-development mailing list