"Peter A. Volchek" wrote:
>
> Before reorganizing the xerces package and update the CVS, many things
> should be done:
> - Changing code
> - Building Xerces on all supported platfoms
> - Retesting Xerces on all platforms
> - Building samples on all platforms
> - Retesting/running samples on all platforms
> - Making a sample that uses Xerces & Xalan (for example). Making sure that
> there are no conflicts
> - Releasing Xerces files with new structure (still not updating CVS)
> - Wait the users callback
> - Fix bugs and missed problems
> -- Meanwhile continue working on Xerces (Schema, ...)
> - And then, announce the new version and update CVS
>
> So, there are things to think about.
While I agree that the change should be tested, I have to say that I
don't understand why you're placing the bar so high. How is this change
so different from any other change we make to the source everyday? Every
change can potentially break any number of the supported platforms. This
one is no exception. So while normal testing should be performed I don't
see why we should do more than we usually do. In particular, packaging
and releasing something that's not in CVS seems plain wrong to me. Are
you saying you want us to release something that only exists on
someone's disk?? I don't think so...
--
Arnaud Le Hors - IBM, XML Standards Strategy Group / W3C AC Rep.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
