We could have a Jenkins job that runs every time the Guidelines builds, and fails if it finds something that will run out in the next X months. Easy to do. Cheers, Martin On 15-03-31 01:55 PM, Syd Bauman wrote:
Yeah. I was on the fence, but I'm mildly happier not trying to rush it in, despite the fact that the change is probably pretty trivial: in those 6 examples that have degree=, change it to precision= with a reasonable value. So in the end I'm with Martin on this.
But personally, I tihnk we should have a better mechanism than raising a ticket to make sure we deal with deprecated items.
I think it's too close to the freeze to do this at the last minute. When we remove examples we should replace them with well-thought-out alternatives, and it's not so easy to do that under the gun.
It's likely that @degree will just about survive into the release after this one, so how about raising a ticket to fix the examples as soon as this release is out, and then although it will still be there in the next, there'll be no examples of it?