search

dotnet / runtime

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
https://docs.microsoft.com/dotnet/core/
MIT License
14.96k stars 4.65k forks source link

Update repo packageIndexes when we ship releases #20301

Closed ericstj closed 4 years ago

ericstj commented 7 years ago

We need a process for committing updates to the packageIndexes in various repros when we ship new releases.

corefx/master and standard/master need updates from corefx/release/1.0.0 and corefx/release/1.1.0. corefx/release/1.1.0 needs updates from corefx/release/1.0.0.

Perhaps this is something maestro can do?

/cc @dagood @chcosta

dagood commented 7 years ago

It seems reasonable to me to use Maestro for this. To make sure it's clear, are you talking about having Maestro detect when release/1.0.0/pkg/.../packageIndexes.json changes and set off a build that creates a PR to change master/pkg/.../packageIndexes.json? (Plus the other subscriptions.)

danmoseley commented 7 years ago

@mellinoe @ericstj marked this blocking-release and you made it future. can you fix one way or another

ericstj commented 7 years ago

If we don't have an automated way to do it we should at least manually do it. The work would actually happen in master not release branch so I guess removing the milestone is ok?

If you'd like, please mark it in a way that doesn't impact burndown metrics since it'd just be tracking manual work that's part of the release.

danmoseley commented 7 years ago

@ericstj if it's necessary to release, it's milestone 2.0 but I marked post ZBB.

Are you doing this - the manual work? I want to assign someone...

ericstj commented 7 years ago

I'll do it, but it cannot be done until we have a stable build of packages.

karelz commented 6 years ago

This is old bug, which was supposed to be addressed in 2.0.0. I assume it is not tracking anything actionable at this point, closing. Feel free to reopen if I am wrong (ideally with more appropriate milestone).