[jboss-dev] M2 planning and timeline

Brian Stansberry brian.stansberry at redhat.com
Tue Jan 12 18:23:45 EST 2010


Ok, thanks.

On 01/12/2010 03:34 PM, Scott Stark wrote:
> I believe that there is a need for a 5.1.x naming release to expose the
> new namespaces so that admin views like JNDIView start working
> correctly. It mostly likely would only include  JBNAME-44 and JBNAME-41
> if we want to drop the default java:comp creation.
>
> 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!
>>
>>
>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development


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



More information about the jboss-development mailing list