-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please update tracking changes documentation #2556
Comments
/cc @noahfalk who wrote the doc and @dagood who's likely changed most of what I'm imagining @ViktorHofer's referring to. |
We aren't pushing to myget anymore therefore we need to update some parts of the doc. Happy to do that 😁 |
Probably lots of those package IDs and what not are wrong now with the 3.0 work as well. |
It should be more straightforward now, broad strokes:
This process should be uniform from CoreCLR through Core-SDK since There is a /cc @mmitche |
@dagood would you mind updating the doc with your details? |
Can do, but I don't know when I'll have time. My comment lists all the stuff I know offhand, I'd have to look more into the scenarios in the doc to find suitable alternatives. Something that would help get started is the entry point. How are you installing the SDK or runtimes that would be best to focus on as the artifact to start tracing from? (Not using NuGet packages as much anymore and not having a reasonably browsable package feed puts a damper on things.) |
@markwilkie is it possible to address this from the Darc side, as part of tooling? Is there a doc about how to track down changes using Darc from artifacts? Marking up for grabs because anyone could figure out what the process is and submit a PR to update the doc. |
[Triage notes] We believe that Arcade should provide a generic way for this, perhaps in Darc. |
According to @ViktorHofer the instructions detailed in https://github.com/dotnet/core-setup/blob/master/Documentation/project-docs/how-to-track-changes.md are out of date. Could you possibly update them? cc @ericstj
The text was updated successfully, but these errors were encountered: