Sanjiva, Yes, i agree that we should lock-down changes at this time or we will never get the product out. I was simply saying that some of the problems occur because of unintentional changes, which can be prevented by a strong test suite early in the cycle.
Thanks, dims --- Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > Hi Guys, > > IMO everyone needs to constrain their changes at this stage if > there is to be any real hope of getting 1.0 out this year. In > stuff I've released, once something in RC stage *nothing* changes > except bug fixes. Changing user-level APIs is absolutely out, as > is changing any internal guts for "cleaner guts" purposes. > > I think Rick's frustration is reasonable. Dims, I find it a bit > hard to accept the position that users should file test cases > for functionality they've gotten used to in a beta/RC stage that > they'd like to keep. The reason to go from alpha to beta is (and > was, even here) to signal to users that things are somewhat stable. > > I suggest that we develop a precise list of what needs to be done > for 1.0 and do *nothing* but that. Reject EVERY other change. Yep, > that's pretty damn draconian, but that's the only way to get such > a big beast like Axis completed and out the door. This is especially > true for 1.0. > > If all committers don't agree to this then I am not at all > confident this will get done in 2002. > > Sanjiva. > > ===== Davanum Srinivas - http://xml.apache.org/~dims/ __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com
