en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/ci/RELEASES-template.md#14226457 Refactor how release notes are managed (#8680)* Refactor how release notes are managedThis commit updates how Wasmtime manages release notes across releasedversions of Wasmtime. One of the most onerous parts about releases rightnow is writing release notes in all the locations and making surethey're all up-to-date and in-sync. This is inevitably forgotten in somecases and various pieces will slip through the cracks. The basic idea ofthis PR is to change our release notes to only document the releasebranch that they're on. All historical release notes are relegated tohistorical branches.With this change there's no longer any need to backport or forward-portrelease notes for any changes. Instead release notes are written onceon one branch and that's it.The major downside of this change is that there's no easy way to get abird's eye view of all release notes for Wasmtime any more. If necessarythat could theoretically be automated in the future (likehttps://releases.rs/), but for now this feels like an acceptablecompromise to make releases much easier.The contents of this PR are to update `RELEASES.md` with back-links tohistorical release notes as well as the various pieces of automation wehave about managing release notes.* Add more notes about the release process* Fix a typo* Make it more obvious that patch releases are documented List of files: /wasmtime-44.0.1/ci/RELEASES-template.md Thu, 23 May 2024 16:35:23 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/ci/RELEASES-template.md#c89dc551 Add a two-week delay to Wasmtime's release process (#3955)* Bump to 0.36.0 * Add a two-week delay to Wasmtime's release process This commit is a proposal to update Wasmtime's release process with a two-week delay from branching a release until it's actually officially released. We've had two issues lately that came up which led to this proposal: * In #3915 it was realized that changes just before the 0.35.0 release weren't enough for an embedding use case, but the PR didn't meet the expectations for a full patch release. * At Fastly we were about to start rolling out a new version of Wasmtime when over the weekend the fuzz bug #3951 was found. This led to the desire internally to have a "must have been fuzzed for this long" period of time for Wasmtime changes which we felt were better reflected in the release process itself rather than something about Fastly's own integration with Wasmtime. This commit updates the automation for releases to unconditionally create a `release-X.Y.Z` branch on the 5th of every month. The actual release from this branch is then performed on the 20th of every month, roughly two weeks later. This should provide a period of time to ensure that all changes in a release are fuzzed for at least two weeks and avoid any further surprises. This should also help with any last-minute changes made just before a release if they need tweaking since backporting to a not-yet-released branch is much easier. Overall there are some new properties about Wasmtime with this proposal as well: * The `main` branch will always have a section in `RELEASES.md` which is listed as "Unreleased" for us to fill out. * The `main` branch will always be a version ahead of the latest release. For example it will be bump pre-emptively as part of the release process on the 5th where if `release-2.0.0` was created then the `main` branch will have 3.0.0 Wasmtime. * Dates for major versions are automatically updated in the `RELEASES.md` notes. The associated documentation for our release process is updated and the various scripts should all be updated now as well with this commit. * Add notes on a security patch * Clarify security fixes shouldn't be previewed early on CI List of files: /wasmtime-44.0.1/ci/RELEASES-template.md Fri, 01 Apr 2022 18:11:10 +0000 Alex Crichton <alex@alexcrichton.com>