You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Prasad Kashyap <go...@gmail.com> on 2007/07/02 16:40:13 UTC

Re: [DISCUSS] 2.0 Release Criteria

On 6/21/07, Matt Hogstrom <ma...@hogstrom.org> wrote:
> We've gone through the CTS grind and came out victorious http://
> java.sun.com/javaee/overview/compatibility.jsp
>
> OpenEJB has moved to TopLevel and CXF has certified and Axis 2 is
> working that way too.
>
> All in all its been an excellent six months.
>
> So, what are we going to do for 2.0 and getting it out the door?
>
> Here are my thoughts and we can use this thread to gather everyone
> else's and come to a consensus.
>
> 2.0 Ship Criteria
> Date:  mid to end of July (a target only...depends on content)
>
> Certified Assemblies
> Tomcat, Axis 2 and OpenJPA
> Jetty, CXF and OpenJPA
>
> Other assemblies would be the minimal assemblies but cert doesn't
> apply to them.
>
> Work on fit and finish stuff (cleaning up error messages, improving
> diagnostics, reducing footprint).
>
> Personally, I'd like to see the full G have a footprint of about 40MB
> (that's a little over 5MB larger than 1.1.1) and Minimal be around
> 20MB.  Need to do some research on this (volunteers?)

Another thing that comes to mind is the runtime footprint. Isn't that
another thing that we should evaluate as a metric ? Thoughts ?

Cheers
Prasad


>
> I'm not sure how the WADI clustering presents itself across the two
> different assemblies (Gianny, comments?)
>
> Post 2.0 Items
>
> What to do about OSGi?  Seems like there has been discussion but no
> real movement in this area.
> Flexible Server (there has been some discussion on the list about
> allowing users without a PhD in G to create their own custom assemblies.
> Would be neat to Create a minimal assemblie that included ServiceMix
> for a lightweight ESB endpoint
> Better monitoring and diagnosis
>
>
> Thoughts?
>