[Issue 11792] Investigate migrating to a meta repo

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=11792

--- Comment #7 from Vladimir Panteleev <thecybershadow at gmail.com> ---
On the forum, I posted ([1]):

> I would like to add that, however, it might be worth considering 
> moving everything to a single repository at the same time as the 
> switch to DDMD. DDMD by itself is a big change, so aggregating 
> other changes with big wolkflow impact (but net benefit in the 
> long run) would make sense.

This would also be a good time to replace makefiles with a D build tool.

Here are some thoughts on how this can be done:

- Create the repo with an experimental status ahead of time, so that it can be
extensively tested.
- Decide on a date on which the switch will occur.
- Add comment to all open pull requests some time before, that the changes will
need to be rebased on the new repository.
- Use git-subtree to add the existing repositories to the new unified
repository.
- Add a commit to the existing repositories which replaces the README (and
possibly all content) with a link to the new repository.
- Move the old repositories to a new organization (e.g.
D-Programming-Language-Old) so they don't clutter D-P-L organization's project
list. TODO: Check if GitHub creates redirects (we need redirects).

Although the change is big, the gain is also big: we will have one single
repository using a self-hosted compiler and build system. By doing these all
together, we will need to break things only once.

[1]: http://forum.dlang.org/post/fjpppbranpbikojvkdxv@forum.dlang.org

--