-
Notifications
You must be signed in to change notification settings - Fork 10.3k
DNX Runtime releases and SemVer #1068
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
Comments
SemVer agrees with the first part of your statement, but not the second. SemVer says that as long as you stay within 1.x, there will be no breaking changes. SemVer says that when 1.x changes to 2.x, there are breaking changes. However, that doesn't necessarily mean that a particular library won't work on 2.x. If the library just uses |
@Eilon thanks! Yes, true but you cannot assume that your library written against 1.x will work on runtime 2.x. So, my questions is: what is the plan for DNX runtimes? Is SemVer is going to be applied for them as it's explained here? Can I always assume that my app/library will survive upgrades within the same major version? |
The idea is to apply SemVer to all packages. So yes, you can safely assume that. |
@Eilon thx! |
Are DNX Runtime packages going to apply SemVer? What I am trying to understand is this: when I rely on DNX runtime 1.0.0 for my library or application, can I assume that it will always work on any runtime releases whose major version is 1 and may not work for any with major version of 2 or higher?
The text was updated successfully, but these errors were encountered: