All,
I just finished making some changes to our BRL-CAD "interface change policy", i.e., the CHANGES file. Have a look and let me know if anyone sees any problems.
The main impetus was to denote how we deal with new interfaces and formalizing a policy that allows new API to change as needed while it's under active development. An additional example was included and the policy portions are now up-front first in the file (including the minimally impacting verbage).
I also simplified the deprecation policy to allow a minimally impacting changes during any release. Comments? Previously, this was only during a minor release but my feeling is that we have much API in flux that needs to change more rapidly than that. The alternative is that nearly every release becomes a minor release (which would be fine).
Cheers!
Sean
------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
