-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Recommended version number scheme for SDK? #2314
Comments
We're in the process of standing up release branches which would make sense for you to follow. For the sdk, picking up the latest from release/3.0.1xx should do the trick. @livarcocc to confirm. |
Got it. But what about the |
All components should be picking up the *-preview{n}-{buildnumber} scheme. |
But the {buildnumber} part is breaking semver and the *-preview part seems not unique. |
Why is the {buildnumber} part breaking semver? It seems complaint to me according to: https://semver.org/#spec-item-9 That said, I don't think we claimed we follow semver, although it would be nice ... |
My point is that translating the version from the
|
I would think that's OK (no "." in the prerelease string)? We're in the process of finishing up Preview 3 (hopefully out Tuesday) and the SDK version will look like |
Okay, it looks like it's possible: https://chocolatey.org/packages/dotnetcore-runtime.install/3.0.0-preview-27324-5 😄 |
For maintainting the dotnetcore-chocolateypackages I want to add
3.0-preview
but I'm not sure what version for the SDK currently is recommended.The SDK version from the releases.json is not
semver
and thelatest-release
tend to be aligned with the runtime and not the SDK.Should I be using the
3.0-preview2
for now and switch to runtime & sdk specific versions when out of preview? Or is thelatest-release
version the way forward and encapsulates this underlying versions?Any advice on this?
The text was updated successfully, but these errors were encountered: