Replies: 3 comments 1 reply
-
Yes, but publishing at every commit is a bad idea due to the amount of resources it consumes at crates.io.
All pre-releases are semver compatible with each other. Plugins will likely only work with a subset of the pre-releases though. Also there may not be a subset which works for all plugins you want.
I think it should just specify the git repo of bevy instead of a pre-release from crates.io. |
Beta Was this translation helpful? Give feedback.
-
I think it's better to have the upcoming big bevy features into a separate branch kept in sync with It doesn't require additional effort or complicating the release process. Edit: Also, if a plugin maintainer wants to keep up with the latest Bevy release as soon as possible, one of their branches (possibly the default branch) should really depend on Bevy's |
Beta Was this translation helpful? Give feedback.
-
I think the ability to target big upcoming features is important. |
Beta Was this translation helpful? Give feedback.
-
See https://doc.rust-lang.org/cargo/reference/resolver.html#pre-releases for pre-releases.
Use pre-releases for bevy to allow plugin maintainers to target the current, pre-release bevy version.
This enables plugin maintainers to target the plugin at bevy between two releases. Therefore plugins must not be locally modified by everyone trying to run it on the current bevy pre-release.
Results in less friction for the individual using up-to-date bevy if someone already published the changes needed for targeting the pre-release.
Things unclear:
Beta Was this translation helpful? Give feedback.
All reactions