News for hackers. Stuff that matters.
Re:The .NET Core 2 Wave by vetinari on Monday January 23, 2017 @10:45AM (#13462933)
Speaking of target audiences using non-Windows systems... how does their versioning work there?

The version labeled 1.0.3 TLS is dotnet-dev-osx-x64.1.0.0-preview2-003156.pkg (1.0.0? preview?)

The version labeled 1.1 is dotnet-dev-osx-x64.1.0.0-preview2-1-003177.pkg (again: 1.0.0 preview?)

The linux packages have similar pattern.

Re:The .NET Core 2 Wave by dsp1234 on Monday January 23, 2017 @12:03PM (#13463637)
"Preview 2" is the tooling version (command line tools). The tools (such as the dotnet command and related binaries) are versioned separately from the framework itself.

This allows the team the ability to release new tooling versions (bugfix to the donet command for example), without having to print a new framework version. Same for updating the framework vs the tooling.

On the one hand, it's annoying to keep track of so many versions. On the other hand, it's also annoying to be forced to run a framework update when the only thing that's changed is a command line tool, which may or may not be important to a specific organizations development pipeline.

Re:The .NET Core 2 Wave by vetinari on Monday January 23, 2017 @01:10PM (#13464310)
Thanks for the explanation, makes sense.
Re:The .NET Core 2 Wave by socrates666 on Monday January 23, 2017 @11:02AM (#13463071)
Microsoft adapted this versioning http://semver.org/ standard.

So, 1.0.0-previewX < 1.0.0.

Semantically this should be read as "1.0.0-previewX is preview X of version 1.0.0"

Re:The .NET Core 2 Wave by vetinari on Monday January 23, 2017 @11:27AM (#13463313)
Then their own labeling does not reflect the versions indicated in the filenames.