Skip to content
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

Announcement: Repository Consolidation Timeline #27549

Open
jaredpar opened this issue Oct 30, 2019 · 8 comments
Labels
Milestone

Comments

@jaredpar
Copy link
Member

@jaredpar jaredpar commented Oct 30, 2019

As we announced earlier we are planning on consolidating some of the repositories in the dotnet org. Our planning has reached a point where we have a schedule for the coreclr, corefx and core-setup moves into dotnet/runtime that we want to share out with the community.

November 13th

We’ll move all changes from the original repositories into dotnet/runtime up to 5PM on November 13th PST (1AM November 14th UTC). We’ll try to help as many pull requests as possible get merged by then. At that point, if there’s any pull requests still open we’ll have to close them. If you’d still like to continue those pull requests, we’d encourage you to bring them to dotnet/runtime in a new pull request.

The repositories themselves will be effectively archived at this point. The state of the “master” branch will be recorded with a tag, named “master-archive”, but the branch itself will be deleted. The default branch for the repositories will be named “archive” and it will be a single commit with a README.md and CONTRIBUTING.md file pointing to our dotnet/runtime repository.

The repositories will remain active for servicing changes to .NET Core 3.1 and earlier hence we will not be using the GitHub archive capability.

November 22nd

The dotnet/runtime repository will be made public and available for community contribution. Even though the repository will be created on November 13th it will take several days to get it back into a working order: fixing up our build scripts, recreating our Azure Dev Ops build definitions, etc … Until those tasks are completed it will not be possible to accept pull request and hence the repository will remain private. Once we are in a state that pull requests can be merged again the repository will be made public.

Our expectation is that will occur on November 22nd. If it is ready sooner it will be made public sooner. If the work takes longer than we planned then we will add an update to this announcement with a new expected date.

December 1st-2nd

All issues, open and closed, will be migrated from corefx, coreclr and core-setup into dotnet/runtime. This will be using GitHub’s existing issue transfer feature in a bulk migration. This means all of the existing issue links will continue to function via redirects.

This does mean though that labels will not transfer with the issues. Labels will be re-applied as a post processing step by our engineering team once the issue migration completes.

Even though our issues won’t be fully migrated until this time we’d like the community to begin filing issues on dotnet/runtime as soon as it’s public rather than continuing to file issues on the original repositories.

Migrating Commits

The dotnet/runtime repository will be a new commit history from the original repositories. We are using this consolidation as an opportunity to clean up our history with the goal of having a cleaner, smaller history as a starting point. This means commits will be rewritten in the following ways as they are migrated to dotnet/runtime:

  1. Author information, contributor information, changed file list and time stamps from the original commit will be preserved.
  2. Links to issues, pull requests or commits in the repository using GitHub short links will be rewritten so they continue to point the original repository.
  3. Every commit will be appended with a link to the original commit it was mapped from.

The actual contents of the commit though will be updated to match the new directory layout of the dotnet/runtime repository.

@jaredpar jaredpar added the area-Meta label Oct 30, 2019
@jaredpar jaredpar added this to the 5.0 milestone Oct 30, 2019
@AaronRobinsonMSFT

This comment has been minimized.

Copy link
Member

@AaronRobinsonMSFT AaronRobinsonMSFT commented Oct 30, 2019

@jaredpar I am going to pin this issue since it is so impacting to the repo and community.

@AaronRobinsonMSFT AaronRobinsonMSFT pinned this issue Oct 30, 2019
@huoyaoyuan

This comment has been minimized.

Copy link
Contributor

@huoyaoyuan huoyaoyuan commented Oct 30, 2019

up to 5PM PST on November 13th.

Could you add a UTC time? Not everyone are familiar with offset of PST.

@jaredpar

This comment has been minimized.

Copy link
Member Author

@jaredpar jaredpar commented Oct 30, 2019

@huoyaoyuan done

@gfoidl

This comment has been minimized.

Copy link
Contributor

@gfoidl gfoidl commented Oct 31, 2019

aspnet/Extensions is also affected (when I read correct).
Please add an announcement over there, as there's no such info so far -- only in the dotnet-org.
Or will aspnet/Extensions brought in later?

@stephentoub

This comment has been minimized.

Copy link
Member

@stephentoub stephentoub commented Oct 31, 2019

Or will aspnet/Extensions brought in later?

When and where its components move is still being investigated. It is not part of this initial consolidation.

This was referenced Nov 6, 2019
@gfoidl

This comment has been minimized.

Copy link
Contributor

@gfoidl gfoidl commented Nov 9, 2019

All issues, open and closed, will be migrated from corefx, coreclr and core-setup into dotnet/runtime.

Will the issue-subscriptions (email notifications) also be transfered / migrated?

@danmosemsft

This comment has been minimized.

Copy link
Member

@danmosemsft danmosemsft commented Nov 9, 2019

Will the issue-subscriptions (email notifications) also be transfered / migrated?

We will be using Github's regular issue transfer feature. @jeffschwMSFT was going to check whether it does this, and if not, what other options we have.

@Eilon

This comment has been minimized.

Copy link
Member

@Eilon Eilon commented Nov 11, 2019

I do believe notification settings are preserved (if you were watching an issue, you're still watching it, and if not, then not).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.