Think this was captured in a procedure somewhere... As far as I know we have one exception - when switching over to a GeoAPI interface ... we did a bit better for Filter recently by being able to make geotools Filter extend the GeoAPI filter for a release, but often this is not possible due to conflicting methods.
Cheers, Jody > I noticed that the "deprecate, then delete" cycle is not always done for > public > API changes, so I added a "Changing public API" section there: > > http://docs.codehaus.org/display/GEOT/5.+5+Refactoring > > 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 > ------------------------------------------------------------------------- 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
