Frank Schönheit - Sun Microsystems Germany wrote: > I'd say we need a set of highly proficient and highly respected > architects, whose opinion should, at least, be weighted high.
No, please not! Every code change can break something, so why should API changes be treated differently? We should keep it simple. The only difference should be that arbitrary code changes can be done at any time while API changes can only be done at certain points in time. We could say: API changes (including changes of language bindings) can be made in every major release, and you can change everything you want. Of course (as for every code change) you should do that accountably and talk to other developers that will be influenced by your changes and you should try to make your changes in a way that the potential work of others is minimized. But please no processes, not gate keeper etc. Let things evolve and assume that all participants in the development process act reasonably. A bad API change should be treated as any other code change or patch that we have nowadays: if you see a problem with it, raise your concerns and discuss. Regards, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[email protected]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
