Hi Mathias, > OTOH we should not leave APIs unpublished for such a long time as in > case of the one we are talking about.
Hmm ... I tend to leave my API unpublished, with the implicit promise to do only "compatible" changes to it, like adding methods or such. At least as long as Jürgen doesn't come up with the long-promised proposal to re-work the API stability concepts :) > As an example, we could mark unpublished stuff in our online > documentation and add a very visible hyperlink to it that points to a > page explaining all that. So nobody will need to scan the DevGuide just > to learn this important peculiarity of our API. Like that idea ... Ciao Frank -- - Frank Schönheit, Software Engineer frank.schoenh...@sun.com - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
