-
Notifications
You must be signed in to change notification settings - Fork 263
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
Adopt standard software management practices i.e. dependency versioning #238
Comments
We're actually working on getting releases out for all the crates right now haha. We ideally should have everything in place to make a release in a couple days |
Ooh awesome! |
Basically, or ideally, these |
Right, the main blocker is arkworks-rs/std#29, and the corresponding downstream PRs. I plan to merge these ASAP. |
Releases are out! Closing this for now, please open new issues if theres any other software development practice's you'd recommend |
It is fairly weird that we are utilising master as the version for downstream dependencies. Perhaps the rationale is that we are not at a release stage of the project yet. Still, it seems wise to start maintaining branches of release versions and in addition to a breakage-prone master? Especially since arkworks is actually being deployed.
The text was updated successfully, but these errors were encountered: