Frank Rehwinkel (Mar 29 2025 at 14:25): Frank Rehwinkel (Mar 29 2025 at 14:25):Hello everyone,
I've been looking again as some Bytecode Alliance projects and noticed some differences in release approaches that I'm curious about:
Is there documentation on the decision-making process between using Git tags versus GitHub releases for versioning?
For Wasmtime, I notice GitHub releases include changelogs, but I don't see a CHANGELOG.md file in the repository. How is this changelog maintained?
Cargo-component appears to have shifted from GitHub releases (up to 0.20.0 in January) to Git tags (currently at 0.21.1). Is there a changelog available for cargo-component?
Generally, I'm wondering if the Alliance or a major project within it has established best practices for version releases and changelog maintenance. If such practices exist, are projects at different stages of adopting them, or is this an area where approaches intentionally vary by project?
Even as I ask, this sounds like busy work that your teams don't have time for, on the other hand, some are working on changelogs and others used to and it seems preview 2 has been out long enough that outside projects are expected to be able to use the pieces but it is hard to follow what is changing, even for versions being published to docs.rs.
Thank you for any insights you can share!
Dave Bakker (badeend) (Mar 29 2025 at 14:29):Wasmtime has https://github.com/bytecodealliance/wasmtime/blob/main/RELEASES.md
Alex Crichton (Mar 29 2025 at 17:11):Each repository in the BA makes its own conventions right now, there's not an over-arching set of conventions everything follows. As Dave pointed out Wasmtime does have a changelog, it's just named a bit differently.
Last updated: Apr 07 2025 at 23:03 UTC