Andrea Aime wrote: > Jody Garnett ha scritto: >> A couple more sanity checks for after a proposal has been accepted: >> - Clean up any code examples to follow the proposed API > This shall be done after the proposal is accepted right? Yes, although frankly code examples are the *best* way to review an API change :-) > This also calls for having an easy way to locate all code examples. > Are they all in the new "demo" module? I think that would be the best way to handle it, the other alternative would be as part of a JUnit test. >> - Provide migration instructions, see wiki for example BEFOR / AFTER >> format > Agreed. This also allows to evaluate the impact of a change, maybe > this should be done along with the proposal, not after. It is needed after, if the person writing the proposal can communicate with out a code example there is no reason to slow them down.
Thanks for moving this along Andrea .. one step at time :-) Jody ------------------------------------------------------------------------- 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
