If code changes are still going in (and its been a long time since the last
RC) shouldn't there be another RC to make sure new regressions have not
been introduced? And what about all of the critical/blocking bugzillas?
Shouldn't they be reviewed before shipping? This goes back to the idea
that if you're going to ask people to test the RC then you should be
prepared to deal with the issues they find otherwise why should they bother
testing it?
-Dug
Glen Daniels <[EMAIL PROTECTED]> on 04/04/2003 02:06:16 PM
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: Axis 1.1 passes the JAX-RPC TCK, VOTE for 1.1 final.
+1 from me, with the caveat that I plan to do this on MONDAY, APRIL 7th.
There are a couple of SOAP 1.2 fixes I need to check in, and I'm planning
to do a last scan for critical stuff / doc updates etc. over the weekend.
--Glen
> -----Original Message-----
> From: Tom Jordahl [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 04, 2003 10:51 AM
> To: '[EMAIL PROTECTED]'
> Subject: Axis 1.1 passes the JAX-RPC TCK, VOTE for 1.1 final.
>
>
>
> I have just gotten news from our test engineer that Axis 1.1
> CVS as of April 3, 2003 has passed the JAX-RPC TCK test suite.
>
> This is the last barrier preventing us from finalizing the
> Axis 1.1 release.
>
> I am calling for a VOTE to label the tree and build 1.1 final kits.
> Here is my +1!
>
> --
> Tom Jordahl
> Macromedia Server Development
>
