-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
1.0.0 release? #73
Comments
I do not recall any particular plan for versioning. We bump it as the package got updated. As for stability, the API haven't changed for years: |
I thought the plan for all accepted Julia packages was to follow this: https://semver.org/ .
I do not understand. Then what's the problem with releasing a version 1.0.0? It is important for people depending here. As instructed by SymVer, you can do whatever change you want to a non-major version. If you release 1.0.0, this would allow us safely to depend on versions As a (very tiny) developer of Julia packages, I don't understand your comment. You can still release a 2.0.0 version if in "years" from now you want to do breaking changes. Please help me understand what "problems" are there in releasing a major version. |
There are no "problems" per se but some outstanding issues. In my opinion, for a proper long lasted release following issues need to be addressed first:
Of course, documentation and examples need to be straighten up. I like |
All things done for 1.0.0 release. It will be out shortly. |
Hi, what's the plan for a 1.0.0 tag? What is left to be done? In general some stability promise would go a long way for developers like us (JuliaDynamics)
The text was updated successfully, but these errors were encountered: