Stream: wasmtime

Topic: release schedule


view this post on Zulip Pat Hickey (Mar 11 2020 at 17:55):

apologies if this was already discussed elsewhere. is (or should) wasmtime on a schedule for regular releases?

view this post on Zulip Pat Hickey (Mar 11 2020 at 17:55):

and, is the version policy to keep everything in the repo at the same crate version?

view this post on Zulip Pat Hickey (Mar 11 2020 at 17:56):

asking mostly because im looking forward to a release of wiggle

view this post on Zulip Alex Crichton (Mar 11 2020 at 17:59):

I don't think we've talked about a release schedule, and we at least are keeping the cranelift/wasmtime verisons separate

view this post on Zulip Alex Crichton (Mar 11 2020 at 17:59):

I think it'd be ok for crates like wiggle to have their own version/release schedule

view this post on Zulip Alex Crichton (Mar 11 2020 at 17:59):

(personally at least)

view this post on Zulip Till Schneidereit (Mar 11 2020 at 18:04):

Agreed: at least for now it should be entirely fine for wiggle to be on its own schedule. Having a regular schedule would be a very interesting thing for perhaps the not too distant future, though!

view this post on Zulip Pat Hickey (Mar 11 2020 at 18:13):

ok, how about for now we just release 0.1.0, and then we will sync it up with the wasmtime version and release schedule for 0.13

view this post on Zulip Alex Crichton (Mar 11 2020 at 18:15):

sounds reasonable to me at least!

view this post on Zulip fitzgen (he/him) (Mar 11 2020 at 18:16):

One thing is that we should take care not to break the publish script: https://github.com/bytecodealliance/wasmtime/blob/master/scripts/publish-all.sh

Standalone JIT-style runtime for WebAssembly, using Cranelift - bytecodealliance/wasmtime

view this post on Zulip fitzgen (he/him) (Mar 11 2020 at 18:17):

oh I thought that was doing the version bump inside the publish script but it looks like it isn't

view this post on Zulip fitzgen (he/him) (Mar 11 2020 at 18:18):

and was worried about whether we were assuming that everything was always on the same version, which might break if we start doing independent releases

view this post on Zulip Dan Gohman (Mar 11 2020 at 18:40):

The tricky part is that you can get into situations where everything in the tree builds and works fine, because it's all using path dependencies on things in the tree, but if the version numbers aren't right, things will break for people using the packages from crates.io


Last updated: Dec 23 2024 at 14:03 UTC