Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
/ corefx Public archive

Update experimental IsShipping and block stable properties #41513

Merged
merged 1 commit into from
Oct 3, 2019

Conversation

safern
Copy link
Member

@safern safern commented Oct 3, 2019

When I moved to use the arcade IsShipping convention, I disabled publishing to NuGet.org for experimental packages. The reasoning of that, is because anything mark as non-shipping, will not make it to NuGet.org.

So we need to mark them only as IsShippingAssembly=false so that the AssemblyInformationalVersion in metadata isn't stable whenever we ship stable. Also, mark them as SuppressFinalPackageVersion so that it doesn't produce a stable version of the package whenever we build those. SuppressFinalPackageVersion is the new BlockStable property: dotnet/arcade#1213

This will need to go into 3.1 in order to ship the experimental packages to NuGet.org.

FYI: @GrabYourPitchforks @tannergooding

cc: @danmosemsft

Copy link
Member

@ViktorHofer ViktorHofer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks right 👍

@GrabYourPitchforks
Copy link
Member

Per our email, I don't really know the finer details of how the build / packaging system works. But I'm supportive of getting the experimental packages available on NuGet.

@safern safern merged commit d217998 into dotnet:master Oct 3, 2019
@safern safern deleted the ExperimentalPackagesStory branch October 3, 2019 16:26
safern added a commit to safern/corefx that referenced this pull request Oct 3, 2019
safern added a commit to safern/corefx that referenced this pull request Oct 3, 2019
@karelz karelz added this to the 5.0 milestone Dec 19, 2019
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants