Good point Martin; I have created the following jira QA blocker against 2.4.0 to ensure the @since and other QA checks are dealt with before 2.4.0 goes out the door: - http://jira.codehaus.org/browse/GEOT-1063 > Could it be that the trouble in building Geoserver against > Geotools-trunk is partially caused by ourself not following our "API > change" policy with enough discipline? I saw some public methods where > the signature was changed instead of adding a new method and > deprecating the old one. It also seem to me that the proposal to add a > "@since 2.4" javadoc tag to every new API is not widely applied. So > how a Geoserver developper is expected to know which API is stable and > which API may fluctuate because not yet commited in a release? > > Martin
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
