<br><br>On Wednesday, November 9, 2011, Tim Schaub <<a href="mailto:tschaub@opengeo.org">tschaub@opengeo.org</a>> wrote:<br>> I should add that I think we should have an explicit deprecation<br>> strategy that encourages people to stop using deprecated code. I'd<br>
> propose that we mark code as deprecated and keep it in the main lib<br>> for one release - including a list of newly deprecated<br>> methods/properties in the release notes. We could leave deprecated<br>> methods in the main lib for one release and then move them to<br>
> deprecated.js. In the subsequent minor release, we wouldn't have<br>> changed the api, but people would have to include deprecated.js to get<br>> the old stuff.<br><br>Hi<br><br>Thanks for putting this patch together. I agree with the approach. We can even hope to release 2.13 quickly after 2.12.<br>
<br>When you say mark code as deprecated do you mean having *deprecated* strings in the API doc strings, or do you also mean displaying deprecation messages in the console?<br><br><br><br>-- <br>Eric Lemoine<br><br>Camptocamp France SAS<br>
Savoie Technolac, BP 352<br>73377 Le Bourget du Lac, Cedex<br><br>Tel : 00 33 4 79 44 44 96<br>Mail : <a href="mailto:eric.lemoine@camptocamp.com">eric.lemoine@camptocamp.com</a><br><a href="http://www.camptocamp.com">http://www.camptocamp.com</a><br>
<br>