Stream: git-wasmtime

Topic: wasmtime / PR #3955 Add a two-week delay to Wasmtime's r...

Wasmtime GitHub notifications bot (Mar 22 2022 at 19:05):

alexcrichton opened PR #3955 from new-release-process to main:

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 https://github.com/bytecodealliance/wasmtime/pull/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 https://github.com/bytecodealliance/wasmtime/issues/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.

Wasmtime GitHub notifications bot (Apr 01 2022 at 15:00):

alexcrichton updated PR #3955 from new-release-process to main.

Wasmtime GitHub notifications bot (Apr 01 2022 at 17:13):

cfallin submitted PR review.

Wasmtime GitHub notifications bot (Apr 01 2022 at 17:13):

cfallin submitted PR review.

Wasmtime GitHub notifications bot (Apr 01 2022 at 17:13):

cfallin created PR review comment:

for maximum clarity it might be good to say here that the PR should not include the security patch at this point (that comes below)

Wasmtime GitHub notifications bot (Apr 01 2022 at 17:36):

alexcrichton updated PR #3955 from new-release-process to main.

Wasmtime GitHub notifications bot (Apr 01 2022 at 18:11):

alexcrichton merged PR #3955.

Last updated: Nov 22 2024 at 16:03 UTC