| [orbit-dev] Towards Git for Orbit: submodules + composite repo? |
|
Hi all, It looks like Orbit is the Last of the Mohicans, the only active Eclipse project that's still using CVS instead of Git. Orbit is indeed different from other projects, since multiple branch of the same bundles are active and built simultaneously. It's not a regular master + feature + maintenance branches model. I have the impression Orbit could be a set of Git repositories: 1 for each bundle, with their tags, like on current CVS. Then there would be a releng Git repo that would contain the build stuff and that would also be a composite repository referencing the right tags of the bundle repositories. Since some recent version of Git, submodules not only allow to reference a given commit, but also a given tag, which would make it easy to do that. Composite repo structure would contain the multiple folders for the multiple version of bundles, for example: * orbit/bundles/ ** javax.servlet_2.3.0 (submodule referencing tag v200806031603 of repo javax.servlet) ** javax.servlet_2.4.0 (submodule referencing tag v200806031604 of repo javax.servlet) ** ... ** javax.servlet_3.1.0 (submodule referencing tag v20140303-1611 of repo javax.servlet) ** javax.servlet.jsp_1.2.0 ((submodule referencing tag v200806031606 of repo javax.servlet.jsp) ** javax.servlet.jsp_2.0.0 ((submodule referencing tag v201101211617 of repo javax.servlet.jsp) ** ... What do you think about it? |