Github label to keep track of deprecated code that shall be removed in a given release?


We have some code deprecated, and we document it will be removed in Clang version 19 (2 releases from now).

Since Clang 19 will take a while to arrive, it can be easy to forget we are supposed to remove that code then. Therefore we were considering creating a Github issue with a special label to track this work.

My question to the community would be: do you have opinions/suggestions as to what that label should be?


Wouldn’t a Milestone make more sense for this? Create them in advance for the clang releases and attach the issues to it?

1 Like

This is actually a great idea, thanks a lot! Make complete sense.