geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Genender" <jgenen...@savoirtech.com>
Subject RE: Attacking M4
Date Tue, 26 Jul 2005 00:28:20 GMT

> -----Original Message-----
> From: sissonj@insession.com [mailto:sissonj@insession.com] 
> Sent: Monday, July 25, 2005 6:01 PM
> To: dev@geronimo.apache.org
> Subject: Re: Attacking M4
> 
> David Blevins <david.blevins@visi.com> wrote on 26/07/2005 
> 07:59:47 AM:
> 
> > Alright, here is the deal on M4.  We have OSCON coming up 
> and from my 
> > experience, if we don't get M4 out the door this week, then 
> we won't 
> > see it till the week after OSCON.  I actually tried to cut 
> M3 at OSCON 
> > last year and we all know how that went.
> > 
> > If we don't get M4 out the door this week, our hopes of 
> having M5 by 
> > the 15th are lost.  Assuming we don't want this to happen, 
> here is my 
> > attack plan:
> > 
> > =ATTACK PLAN==========
> > 
> > LAST ISSUES
> > 
> >    - Undeployment issue (GERONIMO-812, David Jencks)
> >    - Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir, 
> > ServiceMix=>Hiram, tmpOrb=>Dain)
> >    - Web Services startup issue (GERONIMO-785, David Blevins)
> >    - Corba interop problem (GERONIMO-813, Dain Sundstrom)
> >    - Izpack/Tomcat issue (GERONIMO-811, Unassigned)
> 
> See comments below.
> 
> >    - Unknown CTS issues (need to clear up GERONIMO-812 to run it
> > completely)
> > 
> > No sitting on tasks, if you are not going to do it, mark it 
> unassigned.
> > 
> > Issue GERONIMO-811 is unassigned.  Can someone either remove the 
> > Tomcat option from the IzPack installer or add a the link 
> to the wiki?
> 
> Jeff, any comment here?  I can modify the installer to not 
> have the Tomcat option for M4.  I now feel we are better 
> waiting and providing the Tomcat functionality in an unstable 
> build from HEAD or M5, working on making it as simple as 
> possible for the user to configure and provide good 
> documentation with the installation. 

M5 is better IMHO.

> 
> I tried using M4 with Jetty disabled last night and had some 
> problems (ran out of time to debug.. was getting late).  It 
> may be something I did wrong, see mail thread "Problems 
> running DebugConsole on Tomcat, with Jetty removed from plans in M4".

Probably a small issue with the plans...I could look into it.  If we are
talking about a mid/end-August M5, we could wait.  If you want the final
Tomcat plans for M4, I could get that for you as well.  What do you think?  

> 
> John
> 
> > 
> > It seems GERONIMO-809 is actually completed, is that right?
> 
> GERONIMO-809 is complete now.  JIRA being down prevented me 
> from completing it last night.
> 
> 
> > 
> > THE FINAL STUFF
> > 
> > We have to run the TCK on the final binary, which means we need to 
> > allow for a couple days of just testing the actual geronimo-1.0- 
> > M4.zip that people will download.  To even get that far, we need to:
> > 
> >    1. [notes] Create release notes for M4 and check them 
> into the QA 
> > branch
> >    2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> >    3. [dist] Cut and sign the binary and source distributions
> > 
> > We are going to need to be done with the remaining JIRA items above 
> > by like Wednesday (best) or Thursday morning in order to do 
> the above 
> > tasks.
> > 
> > I am willing to take care of the svn and dist work. 
> Side-note: I have 
> > to go to a wedding on Friday, so I personally would like to 
> shoot for 
> > Wednesday as Thursday night is too late for me.
> > 
> > Aaron, you willing to do the nice release notes like you did for M3?
> > 
> > ====================
> > 
> > Sound good to everyone?  Going to assume a lazy consensus otherwise.
> > 
> > -David
> > 
> 
> This e-mail message and any attachments may contain confidential, 
> proprietary or non-public information.  This information is intended 
> solely for the designated recipient(s).  If an addressing or 
> transmission 
> error has misdirected this e-mail, please notify the sender 
> immediately 
> and destroy this e-mail.  Any review, dissemination, use or 
> reliance upon 
> this information by unintended recipients is prohibited.  Any 
> opinions 
> expressed in this e-mail are those of the author personally.
> 



Mime
View raw message