We've released 0.12.0 to crates.io and the .NET nuget package.
I think we should add a CHANGELOG.md to track release changes as well as include the relevant part to the GitHub release entry's markdown (right now each release only contains the tagged commit message, which is usually a version bump).
I'm always a fan of changelogs myself
we can edit the new contributing-release-process.md
as a reminder :D
also it can help to have an unreleased section, so people can add notable things to it as they land them
Minor request: could we call it NEWS.md
or RELEASE-NOTES.md
rather than CHANGELOG.md
? To me, "NEWS" implies release notes, while "CHANGELOG" implies commit-by-commit details.
I would personally lean towards CHANGELOG.md just because it seems to be the most popular convention
Rust uses RELEASES.md
. I haven't seen a project that uses CHANGELOG.md
for release notes. and in general if I see a file named "changelog" I tend to automatically ignore it as likely redundant with git log
.
I'm :+1: on RELEASES.md
I've sent a PR for RELEASES.md
at https://github.com/bytecodealliance/wasmtime/pull/1011
Last updated: Dec 23 2024 at 13:07 UTC