Stephan Bergmann wrote: > On 04/30/09 12:24, Mathias Bauer wrote: >> 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. > > "Everything you want" sounds a bit too laissez fair for my taste. > "Everything that is considered worth it, given that each incompatible > changes comes at a cost" would be the long version.
I didn't expect that a reasonable developer would want anything else. :-) But yes, of course, "the long version" is better. Ciao, 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]
