On 06/08/2015 04:43 PM, Stephen Kelly wrote: > In fact, I added that in response to someone on SO recommending setting > policies to OLD and pointed them to the commit and the generated docs, and > they're still recommending the same thing as SO answers. Policies are alive > too long to be credible pending error-conditions. They look like - and are > treated as - feature toggles.
Given the existing docs you quoted I don't think any further docs such as release notes will help. We would need to add a runtime warning to draw attention to pending removal. It would be different than the current "not set" warning and instead be "not set to NEW". -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
