When a group wants to tell their customers that they're shipping with a "fixed" level of Axis and that "fixed" level is changing as much as the nightly build then its no longer "fixed". Any release whether its an alpha, beta or any other kind should have a period in which people bang away at it and report any bugs they see (which did happen) - what was missing was the determination of what will happen to those bug reports. Quite a lot of them were fixed but some were not - at the same time the number of changes made to the source itself never slowed down. Typically, the number of code changes _should_ come as close to zero as possible right before a product is shipped. That did not happen - in fact from the outside it appears the exact opposite happened. I would suggest that a list of all known "issues" with the beta be made and discussed/reviewed - and those that are serious enough that they should have stopped the beta be fixed immediately and a new beta cut. All others should be pushed out to the next release. -Dug
Glyn Normington/UK/IBM@IBMGB on 03/18/2002 12:10:12 PM Please respond to [EMAIL PROTECTED] To: undisclosed-recipients:;, [EMAIL PROTECTED] cc: Subject: RE: Respinning the beta (was: Re: Install doc) Tom Jordahl wrote: >I am +1 for a single respin of beta 1, ASAP (Tuesday AM at the latest). +1 >When users find and report bugs, that is what beta 2 is for. :-) What's wrong with fixing bugs in the beta as we go and rebuilding the beta distribution automatically overnight from the beta branch? Until we ship beta 2, shouldn't we be prepared to fix any severe problems in beta 1? Glyn
