----- Original Message ----- From: "James M Snell" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, February 18, 2003 18:18 Subject: Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning
> I recommend that we do a RC2 release anyway. Freeze the development, test > for obvious errors, give it a week, release, all done. :-) +1 > > - James Snell > IBM Emerging Technologies > [EMAIL PROTECTED] > (559) 587-1233 (office) > (700) 544-9035 (t/l) > Programming Web Services With SOAP > O'Reilly & Associates, ISBN 0596000952 > > Have I not commanded you? Be strong and courageous. > Do not be terrified, do not be discouraged, for the Lord your > God will be with you whereever you go. - Joshua 1:9 > > > > "Steve Loughran" <[EMAIL PROTECTED]> > 02/18/2003 09:30 AM > Please respond to axis-dev > > > To > <[EMAIL PROTECTED]> > cc > > bcc > > Subject > Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, > throwing ClassCastException when assigning > > > > > ----- Original Message ----- > From: "Glen Daniels" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, February 17, 2003 20:35 > Subject: RE: DO NOT REPLY [Bug 16844] - MapDeserializer creates only > HashMaps, throwing ClassCastException when assigning > > > > > > James writes: > > > In the meantime, if others can start working through the bug > > > list also, it would be very helpful :-) > > > > +1! Post-release donuts are on me if we can get a good percentage of > these bugs resolved. :) > > As someone with no qualms about shipping stuff with known bugs (in > preference for shipping stuff with unknown bugs), I want to remind people > that we agreed to only work on critical bugs between RC1 and 1.1 final. > > Any change can introduce unforseen consequences, and it is the last minute > quick fixes without a full beta-test that often turn out to be > troublespots > in shipping code, primarily because without the widespread tests there is > no > way to find out what the consequences of the change are. > > If everyone is going to rush ahead patching things, then we are going to > have to do an RC2 release, completely lock down the CVS branch to all but > the most critical defects, then ship the final product two weeks later. > > > >
