Publishing of experimental packages

[jkotas]

Experimental packages System.Runtime.Intrinsics.Experimental, System.Utf8String.Experimental should:

• Not built in release branches
• Not published on nuget.org

More context #33357 (comment)

[jkotas]

@safern Are you the right person to look into this?

[safern]

@safern Are you the right person to look into this?

Yeah I'm who has worked most with IsShipping* properties to set the right outputs on official builds.

I'm assigning myself and when I have some bandwidth I'll look into it. If @Anipik or @ViktorHofer can take it first, they can happily take it. I'll ping the issue whenever I start looking into fixing it.

[safern]

I added System.Numerics.Tensors to the list as it is marked as experimental as well. I guess we want the same behavior for that one?

https://github.com/dotnet/runtime/blob/master/src/libraries/System.Numerics.Tensors/Directory.Build.props#L5

[GrabYourPitchforks]

If we do end up removing these packages from nuget.org, we should have readmes that provide very clear acquisition steps. For the experimental Utf8String package, for instance, we have a single-line install-package command listed prominently at the top of the readme.

https://github.com/dotnet/runtime/blob/master/src/libraries/System.Utf8String.Experimental/README.md

Feel free to use this as inspiration for the other packages as well.

[eerhardt]

I added System.Numerics.Tensors to the list as it is marked as experimental as well. I guess we want the same behavior for that one?

I see that package as different from Experimental packages, which is why we didn't add the word Experimental to the package ID.

The difference, in my mind, is we NEVER intend to stabilize an XXX.Experimental package - that's why we put Experimental in the name. It may contains APIs that will eventually ship stable somewhere else, but this package itself (named with Experimental) will never ship.

For System.Numerics.Tensors, this is a pre-release version of a package that we have intentions to publish a stable version in the future (or at least we had intentions at the time - I'm unclear on the current plans).

[danmoseley]

What is the status of API review of System.Numerics.Tensors - didn't at least part of it go through review?

[eerhardt]

What is the status of API review of System.Numerics.Tensors - didn't at least part of it go through review?

Yes it was reviewed and marked api-needs-work:
#24385 (comment)
#24385 (comment)