apologies if this was already discussed elsewhere. is (or should) wasmtime on a schedule for regular releases?
and, is the version policy to keep everything in the repo at the same crate version?
asking mostly because im looking forward to a release of wiggle
I don't think we've talked about a release schedule, and we at least are keeping the cranelift/wasmtime verisons separate
I think it'd be ok for crates like wiggle to have their own version/release schedule
(personally at least)
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!
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
sounds reasonable to me at least!
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
oh I thought that was doing the version bump inside the publish script but it looks like it isn't
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
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: Nov 22 2024 at 16:03 UTC