Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release the crate on Cargo #37

Open
oowekyala opened this issue Dec 2, 2022 · 1 comment
Open

Release the crate on Cargo #37

oowekyala opened this issue Dec 2, 2022 · 1 comment

Comments

@oowekyala
Copy link
Collaborator

Currently LFC is bound to a specific git revision of the crate, not a semantic version number. Using semver would allow us to publish bugfixes to the runtime without needing to upgrade LFC. But we also would need to maintain compatibility with the code generator, and also commit to the stability of the ReactionCtx and related user-facing APIs. I don't think the crate is stable enough right now to allow this.

If we start doing that, then we need a defined release cycle, possible using beta versions for all major versions that are not directly used by a released LFC version. Otherwise we will either clutter Crates.io with deprecated, unsupported releases.

@lhstrh
Copy link
Member

lhstrh commented Dec 5, 2022

For what it's worth, I don't think reactor-ts is all that stable either. If there are many releases because there is a lot of development, then I think that is considered a good thing, not "clutter."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants