It's incomplete and just wastes a growing amount of space every release.
People who want to read them can still get them from their respective releases/tags.
It's incomplete and just wastes a growing amount of space every release.
People who want to read them can still get them from their respective releases/tags.
Any reason for the new PR? I was happy to modify the one I've got open if the consensus was to dump these.
Oh, thought you were suggesting making a PR for it. Oh well.
People who want to read them can still get them from their respective releases/tags.
Usually we finish writing release notes after the tag has been made, so I don't think that will be the case. Unless we make a concerted effort to finish release notes before tagging.
Usually we finish writing release notes after the tag has been made, so I don't think that will be the case.
AFAIK that's only happened once, by accident. It also means the software ships with the incomplete notes if so.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
No conflicts as of last run.
I think we should keep the release notes for this release cycle, and open the question on the usefulness of these docs at a later point
Although 23.0 release notes were missing the big PR list, I sometimes found that useful when doing codebase archeology as an additional tool to spot changes.
Also another point previously mentioned from Murch on IRC.
Given the comments here, and additional comments in IRC, there doesn't seem to be consensus on removing these. Going to close this for now.