Consider changing RC versioning pattern

[glucaci]

With the current versioning pattern in nuget.org is not listed the latest released package.

e.g.
OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs

• listed as latest: 1.0.0-rc9
• really latest: 1.0.0-rc10

This can be fixed with the following pattern: 1.0.0-rc.10
This is the same pattern already used for beta releases.

Thanks!

[tomkerkhove]

Bumped into this yesterday myself and agreed it would be nicer. VS also didn't consider 1.0.0-rc10 to be an update for 1.0.0-rc9.

[cijothomas]

Agree. Will keep this mind for next releases.
(alternatively, never do more than 9 rcs/betas/alphas 😄 )

[cijothomas]

For the instrumentation packages, we can now start using 1.0.0-rc9.1,1.0.0-rc9.2,... etc.
1.0.0-rc10 can be unlisted from nuget as it'll be misleading.

1.2 Release
for core packages, we can continue with the current pattern for 1.2 release (i.e 1.2.0-rc1,...1.2.0-rc7 etc The 1.2 stable is coming soon and we dont anticipate rc count to hit 10).

Post 1.2 Release
for core packages, starting with 1.3, we can do 1.3.0-alpha.1, 1.3.0-beta.1, 1.3.0-beta.2, 1.3.0-rc.1, 1.3.0-rc.2, ...1.3.0-rc.11, ... 1.3.0

[cijothomas]

For the instrumentation packages, we can now start using 1.0.0-rc9.1,1.0.0-rc9.2,... etc. 1.0.0-rc10 can be unlisted from nuget as it'll be misleading.

1.2 Release for core packages, we can continue with the current pattern for 1.2 release (i.e 1.2.0-rc1,...1.2.0-rc7 etc The 1.2 stable is coming soon and we dont anticipate rc count to hit 10).

Post 1.2 Release for core packages, starting with 1.3, we can do 1.3.0-alpha.1, 1.3.0-beta.1, 1.3.0-beta.2, 1.3.0-rc.1, 1.3.0-rc.2, ...1.3.0-rc.11, ... 1.3.0

This is done.
1.2.0-rc4 of core packages released.
1.0.0-rc9.1 of non core packages released.
1.0.0-rc10 of non packages unlisted from nuget.

Closing this issue - if any further issues, please open a new one.

[paule96]

@cijothomas

Sorry for the notification. It was just the issue that 1.9 and 1.9.1 are not the same packages... So I just reread the sample and applied the changes and now it's working.

this release looks a bit unstable. I get with the new packages in my Programm.cs the following error:

It complains this on that lines:

builder.Services.AddOpenTelemetryMetrics(builder =>
{
    builder.AddAspNetCoreInstrumentation();
    builder.AddHttpClientInstrumentation();
    builder.AddOtlpExporter(options =>
    {
        options.Endpoint = new Uri("http://otel-collector:4317");
    });
});

[glucaci]

There is no 1.9 or 1.9.1 version, it's only 1.0.0-rc9.1 for non-core packages and 1.2.0-rc4 for core packages.

Make sure that you update all the packages. Seams that is a version incompatibility.
MetricReaderType was removed in 1.2.0-rc4 https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.2.0-rc4

[tillig]

(For future readers...) This happens because the semver pre-release tag is sorted alphabetically rather than numerically. It's convenient that -alpha sorts alphabetically before -beta and that -rc follows, but -rc9 sorts alphabetically after -rc10 which is why it shows up later.

The .NET Core team also has accidentally hit this - early in the .NET Core days (back when the command line was still dnx and projects were going to be JSON format) they also did this -rc9 and -rc10 sort of thing and upgrades failed for a while.

In SemVer 2 they added a concept of "comparing each dot separated identifier from left to right" which I don't think was there at the time. Dots are more significant in delimiting numeric from alphabetic segments than they once were.