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

Build the platforms package for shipping #42940

Merged
merged 3 commits into from
Jun 25, 2020
Merged

Build the platforms package for shipping #42940

merged 3 commits into from
Jun 25, 2020

Conversation

Anipik
Copy link

@Anipik Anipik commented Jun 25, 2020

This #42928 change was mistakenly merged preemptively before the branch was open.
It lacked the packaging stuff, so just adding that

@Anipik Anipik changed the title Packages2 Build the platforms package for shipping Jun 25, 2020
@@ -194,7 +194,8 @@
"2.2.1",
"2.2.2",
"3.0.0",
"3.1.1"
"3.1.1",
"3.1.2"
Copy link
Member

Choose a reason for hiding this comment

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

Do we want to produce a stable package in the next build? Why are we changing this?

Copy link
Author

Choose a reason for hiding this comment

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

yes we want a new stable version of the package in july/next release.

Copy link
Member

Choose a reason for hiding this comment

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

But that should be driven by the property that we set to produce stable packages which will update the index.json file automatically as part of the build, right?

Copy link
Author

Choose a reason for hiding this comment

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

no we dont have that for 3.1, i am the one that generally does it. Sometimes it gets missed and then done after the release

Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

I think you're miss-understanding me. We update it once we've shipped the stable packages and prepare for the next release, but in order to produce stable packages we run this target:

<Target Name="UpdatePackageIndexWithStableVersions"
BeforeTargets="BuildAllProjects"
Condition="'$(DotNetFinalVersionKind)' == 'release'">

When DotNetFinalVersionKind is release. That target will get the packages we're building, will update the packageIndex.json in the build machine before building the packages and will produce stable packages.

Then, once we ship those to NuGet, you go and check-in those changes.

However, doing it here seems wrong, cause if we do a build were DotNetFinalVersionKind != release we will produce non-stable packages for all built packages of this release, and stable package for the platforms package.

Do you see what I'm saying?

Copy link
Member

Choose a reason for hiding this comment

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

This is consistent with how we've been doing it in 3.1

Hmm then how do we produce non-stable servicing releases? That is the point of the target I pointed above.

Copy link
Author

Choose a reason for hiding this comment

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

we no longer produces non-stable servicing release

Copy link
Member

Choose a reason for hiding this comment

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

Ah ok, that is what was confusing me.

Copy link
Author

Choose a reason for hiding this comment

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

I think we should be good either way

@wtgodbe
Copy link
Member

wtgodbe commented Jun 25, 2020

Test failure unrelated

@wtgodbe wtgodbe merged commit 730e2f7 into dotnet:release/3.1 Jun 25, 2020
@Anipik Anipik deleted the packages2 branch October 28, 2020 20:15
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.

4 participants