Hello all, My (current) thoughts on the new release question: I'm not sure about cutting 1.10 to fix just this defect. Given that it can be fixed in the latest CF-1.10 draft, is that not sufficient to tide us over to the whenever CF-1.10 is released? A few years ago we agreed that one release, or perhaps two releases, per year was a good balance; which to me, at least, means that any extra release in the year should be reserved for either getting new functionality out to users with production time constraints, or else correcting a serious error. I'm not sure that this defect (important as it is!) adds new features, nor warrants the "serious" label.
I like the idea of per-release history entries, and "(No) change agreed" issue labels. I would find those very useful. [Daniel wrote](https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1006644633__;Iw!!G2kpM7uM-TzIFchu!hOibaETdBKBrgpir550s20Qgv0K4JPNqTVGMPwPWHbh_TsLOJvVB3rqUEqcGtYbWStY00KX05FY$ ): > 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. That is exactly what I did when applying many of those milestones - and it was indeed laborious. Labelling them at merge-time would be a great addition to the workflow. Setting a milestone on a PR (or issue) is very similar to setting a label - it's on the right hand panel just below where the label-setting feature is. I have just created a 1.10 milestone (via https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/milestones__;!!G2kpM7uM-TzIFchu!hOibaETdBKBrgpir550s20Qgv0K4JPNqTVGMPwPWHbh_TsLOJvVB3rqUEqcGtYbWStY0SJa4pZs$ ). Thanks, David -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1006955695__;Iw!!G2kpM7uM-TzIFchu!hOibaETdBKBrgpir550s20Qgv0K4JPNqTVGMPwPWHbh_TsLOJvVB3rqUEqcGtYbWStY0sY8vyaw$ 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].
