Hi there! I was wondering where's the planned next release of Wasmtime, so we can decide whether to wait for a release, or to maintain a fork of our own to cherry-pick some fixes that are of particular interest to us. I've looked at the RFC and what it says is This RFC proposes releasing Wasmtime on Tuesday every 4 weeks. The precise date of each release may be adjusted to avoid coinciding with public holidays, though, which could result in some releases being a slightly different width apart.
. So I can proooooobably compute the next release date based on the previous one, but that might be imprecise because of the second sentence. Is there a list of releases with associated dates somewhere, that I missed? (If not, would it be interesting to set up something like that?) I'm thinking about something simple, consider: https://wiki.mozilla.org/Release_Management/Calendar but with even fewer columns, only version number and date. Could come also pretty handy to answer specific queries like "knowing the date of a commit, in which release is it?" with a quick glance at such a table.
Until we figure out a better system to manage this the current logic is gated here which is:
tl;dr; next relase probably around dec 5
Good to know, thanks!
Benjamin Bouvier has marked this topic as resolved.
Hey folks! I don't need a new release urgently, but it's now past day-of-month 5 and I don't see a version bump PR having been created?
Looks like the publish bot panicked: https://github.com/bytecodealliance/wasmtime/runs/4419646007?check_suite_focus=true
think we need to make cranelift-codegen
's dep on isle
exact
I think we can retrigger the job after this PR merges: https://github.com/bytecodealliance/wasmtime/pull/3587
Hi All. I haven't seen a port to Dart/Flutter. I was thinking of tackling this myself. Should i start by looking at the Rust, Go or Python embedded projects?
I'd recommend taking a look at wasmtime-{dotnet,py,go,cpp} in the bytecodealliance org as a starting point. None of them are as "complete" as the Rust API per-se because they're all based on the C API which is less "complete" than the Rust API, so starting from the Rust API may not be your best bet to start off with (but we can of course add anything necessary to the C API over time)
Ok great! Thanks.
not sure how my girlfriends picture is my profile picture. Lol
Last updated: Nov 22 2024 at 16:03 UTC