[prev in list] [next in list] [prev in thread] [next in thread] 

List:       geronimo-dev
Subject:    Re: Nearing testing complete ... what should the release name be and next steps
From:       David Jencks <david_jencks () yahoo ! com>
Date:       2007-05-31 17:56:27
Message-ID: 36E88A63-2A2C-49A8-B4DC-A263B38CD2A7 () yahoo ! com
[Download RAW message or body]


On May 31, 2007, at 9:53 AM, Matt Hogstrom wrote:

> There has been lots of work going on to get Geronimo 2.0 certified  
> and it seems like the light at the end of the tunnel is not an  
> oncoming train but the other side :)  With that we're also at the  
> point of cutting a milestone since we're at the end of May.  Given  
> that all possible assemblies won't be fully tested what do folks  
> think about the name of the release and what will it contain?   
> Also, when is a branch appropriate?
>
> I was thinking geronimo-tomcat-jee5-2.0-M6.  This would include  
> Tomcat, CXF and OpenJPA as the components.  The M6 indicates a work  
> in progress but allows us to claim a specific release as certified  
> and allows us to continue knocking off the corners for performance,  
> footprint, etc.

Why not also a jetty assembly?  Unless there are really significant  
problems I'd be in favor of waiting a couple days and getting both  
platforms out at the same time.

>
> It would also seem about right to branch into branches/2.0 at this  
> time as we finish the other work.
>
> What do others think?
>

I have a significant security refactoring I've been working on that I  
would like to get into the next 2.0 official whatever (milestone,  
snapshot, release...) since it is not backwards compatible.  It  
affects how default subjects and run-as subjects are constructed and  
will finish the JACC plugability work.  I'll try to get something out  
today describing how it works in more detail.

thanks
david jencks

> Matt

[prev in list] [next in list] [prev in thread] [next in thread]