-
Notifications
You must be signed in to change notification settings - Fork 20
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
[Feature]: Fixed LIGO Versions #959
Comments
Similar to the request from Miro. |
@hu3man instead of having to specify the version in the command, I think we should use the latest stable version and fix the version in our code internally (and not use the latest tag). |
I agree we should have a stable version per release. I think we just need to make clear what version is being used, both in documentation, but maybe via a cli command as well |
Normal developers require latest stable version
Experimental developers (like me) require next unstable version
Le mar. 16 août 2022 à 06:03, Houston ***@***.***> a écrit :
… I agree we should have a stable version per release. I think we just need
to make clear what version is being used, both in documentation, but maybe
via a cli command as well
—
Reply to this email directly, view it on GitHub
<#959 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATLHMCLWEXDYZY4P5KFNP3VZMHK7ANCNFSM53A5P7YA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Closing as duplicate of #798 |
Describe the feature you would like
add a specific version of LIGO, not the latest that could be unstable
Is this feature solving a problem?
lastest is often unstable, do not use it and specify a version of ligo
Please share any additional details you have?
Details about the problem your feature solves
Code of Conduct
The text was updated successfully, but these errors were encountered: