On Tue, May 1, 2012 at 10:29 PM, Christopher Sean Morrison <[email protected]> wrote: ... > I've just finished clarifying the language and provided a specific > example for extra measure. It reduces the window to three > releases (two including the announcement, removed on or after the third > minor). > So if you deprecate in 7.21 or 7.22, then you can remove in 7.26+. ... > I know we can turn around updates that quickly with most of our internal > codes, > so the concern is primary with external code developers. > For that, I'm looking to you guys (Daniel, Tom, ..) that integrate our libs > with other codes and have to deal with API deprecation on a
I don't have a problem with the policy, Sean. As you know, however, I believe there should be some way to identify the release one is using with compile time macros. Best regards, -Tom ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
