@JonathanGregory I agree that a per-release entry in History would make sense.
What you propose regarding labels would work, although it might be simpler if we track them by pull requests. This is a common pattern in the software development world. This has been made easy for 1.9 as shown by [this filter](https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pulls?q=is*3Apr*is*3Aclosed*sort*3Aupdated-desc*milestone*3A1.9__;JSslKyUrJQ!!G2kpM7uM-TzIFchu!ivMSC2HJq-YCLwK0BeitySBXv3CAIO1p9skWWONzVAEI2DPu_4Wcznuylq7VMXtvkx341r-KSb4$ ) showing those PRs that were manually tagged as going into 1.9. If we were to do that again for 1.10 we would have such an overview, and the PRs would of course link back to their respective issues. Barring that, this can be discovered by pulling up closed PRs and sorting by date, then checking what was merged into `main` between releases - that is however more laborious, so labeling the PRs pre-merge would be the most expedient in my view. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1006644633__;Iw!!G2kpM7uM-TzIFchu!ivMSC2HJq-YCLwK0BeitySBXv3CAIO1p9skWWONzVAEI2DPu_4Wcznuylq7VMXtvkx345Y6bHxM$ 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].
