On Wednesday, November 9, 2011, Tim Schaub <tsch...@opengeo.org> wrote: > I should add that I think we should have an explicit deprecation > strategy that encourages people to stop using deprecated code. I'd > propose that we mark code as deprecated and keep it in the main lib > for one release - including a list of newly deprecated > methods/properties in the release notes. We could leave deprecated > methods in the main lib for one release and then move them to > deprecated.js. In the subsequent minor release, we wouldn't have > changed the api, but people would have to include deprecated.js to get > the old stuff.
Hi Thanks for putting this patch together. I agree with the approach. We can even hope to release 2.13 quickly after 2.12. 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? -- Eric Lemoine Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac, Cedex Tel : 00 33 4 79 44 44 96 Mail : eric.lemo...@camptocamp.com http://www.camptocamp.com
_______________________________________________ Dev mailing list d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/openlayers-dev
