> @JonathanGregory I agree that a per-release entry in History would make sense.
OK. If others agree, this is something we could introduce in 1.10, and it might not be too hard to insert those headings for all the previous versions. > What you propose regarding labels would work, although it might be simpler if > we track them by pull requests. ... 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!h1cVF0ZY_-rnSXxaKt6O3ektrxVFu9le3PS-9SdJ89aMd1smc48A9OhKLSNWiwFbMoc5PeLCVQk$ > ) showing those PRs that were manually tagged as going into 1.9. ... > Labeling the PRs pre-merge would be the most expedient in my view. Thanks. That is neat. How do you tag the PRs in this way? I agree that it would be sensible to do that as it is agreed that a PR will be merged at the next release. However, this doesn't tag the issues, does it? Therefore I think it would still be useful to add a label to the issue once it's agreed to update the convention, for instance "Change agreed". This label would remain forever, and by following the link in the issue to its PR, tagged in the way you describe, you could find out which version it affected. I would also propose a complementary label "No change agreed", to be applied to any issue which we close because it doesn't seem that it's going to reach a conclusion. Of course any closed issue could be reopened and the label removed. I feel that it's better to close issues than to leave them forever dormant. Do others agree, or am I being tempted by excessive tidiness? -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1006751005__;Iw!!G2kpM7uM-TzIFchu!h1cVF0ZY_-rnSXxaKt6O3ektrxVFu9le3PS-9SdJ89aMd1smc48A9OhKLSNWiwFbMoc5UPAXQNc$ 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].
