Merlin Fisher-Levine: can you please review this small change to the dev guide, since you were the one who complained about it on slack? Please let me know if there's a way to word it that would make the intent clearer.

As-built docs: https://developer.lsst.io/v/DM-22507/stack/deprecating-interfaces.html

As Tim pointed out in a thread on Slack, "before" could mean "any time before" and "after" could mean any time after, so the only way not to be ambiguous is to say "in". However, I also think that people might, for some reason, not want to commit to removal in a specific version, so I don't really know what to do.

To be clear, I never cared or found things ambiguous, I just had a reason to innocently check that a message meant exactly what it said, I never meant to make this level of trouble, so basically my review is "your changes look fine to me, but I also never thought there was a real problem, so do whatever you feel makes it most clear".

I think we have converged on "after" because it gives us the flexibility to not quite be able to get around to removing something when the next release is being prepared.

Thanks Merlin Fisher-Levine: I think it was useful to make the "why" messages more explicit in the examples anyway, so people have something to refer to when writing their own deprecation messages.