Dear @davidhassell Thanks for explaining about milestones. As a test I have just attributed the [closed issue about lossy compression by coordinate sampling](https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/327__;!!G2kpM7uM-TzIFchu!jKwQhdcB1F3gJcezSDgXZxVKmnZBKVAz1ut83Xn79F6kDlV_Fu8h3zyKHM8v_P-lgp58GQyNKXk$ ) to milestone 1.9. That is obvious when you open the issue, but you don't see it in the list of issues or when hovering on the issue, so a label saying "Change agreed" would be separately useful still. You can also filter the issues as Daniel showed for PRs. [Filtering the closed issues for the 1.9 milestone](https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues?q=is*3Aissue*is*3Aclosed*milestone*3A1.9__;JSslKyU!!G2kpM7uM-TzIFchu!jKwQhdcB1F3gJcezSDgXZxVKmnZBKVAz1ut83Xn79F6kDlV_Fu8h3zyKHM8v_P-lgp586HawF-U$ ) now shows just the one I have tagged.
It's OK not to make a special release in order to fix this defect if we're sure there's not much danger of anyone coding `Conventions` as 1.8 instead of 1.9 without thinking about it. Cheers Jonathan -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1007408268__;Iw!!G2kpM7uM-TzIFchu!jKwQhdcB1F3gJcezSDgXZxVKmnZBKVAz1ut83Xn79F6kDlV_Fu8h3zyKHM8v_P-lgp58QfEEeXg$ You are receiving this because you are subscribed to this thread. Message ID: <cf-convention/cf-conventions/issues/345/[email protected]> This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
