Description
Landing the migration branches replaces the contents of several repositories' default branches, and the histories will show a merge rather than an ordinary sequence of commits. Anyone tracking those branches, carrying patches against them, or building from a checkout of them will notice, and they should hear about it from us before it happens rather than discover it afterwards.
The community needs to know which repositories are affected, roughly when the landings will happen, what changes for someone consuming these repositories today, and what someone with in-flight work against the old default branch should do about it. It should also be clear where the old contents continue to live, so nobody assumes the previous state has been lost.
This should go out far enough ahead of the landings to give people time to respond, and it should invite that response, since an objection is easier to accommodate before the merge than after. The landings in this epic are blocked on it.
Description
Landing the migration branches replaces the contents of several repositories' default branches, and the histories will show a merge rather than an ordinary sequence of commits. Anyone tracking those branches, carrying patches against them, or building from a checkout of them will notice, and they should hear about it from us before it happens rather than discover it afterwards.
The community needs to know which repositories are affected, roughly when the landings will happen, what changes for someone consuming these repositories today, and what someone with in-flight work against the old default branch should do about it. It should also be clear where the old contents continue to live, so nobody assumes the previous state has been lost.
This should go out far enough ahead of the landings to give people time to respond, and it should invite that response, since an objection is easier to accommodate before the merge than after. The landings in this epic are blocked on it.