[eclipse-dev] git migration - Platform UI, Platform Runtime, e4 tools an

[Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>]

I'm still working on the map files, but our git conversion is almost over.  From this point on, please consider Platform UI (and forms/browser in eclipse.platform.ui), Platform Runtime (eclipse.platform.runtime), E4 Tools (e4/org.eclipse.e4.tools) and E4 UI (e4/org.eclipse.e4.ui) CVS read-only and our git repos live.

E4 Tools
git://git.eclipse.org/gitroot/e4/org.eclipse.e4.tools.git
- Use master for e4 0.12

E4 UI
git://git.eclipse.org/gitroot/e4/org.eclipse.e4.ui.git

Contains some e4 demos that depend on other parts of e4, and our simple IDE work.
- Use master for e4 0.12

Platform Runtime (plus Eclipse4 runtime)
git://git.eclipse.org/gitroot/platform/eclipse.platform.runtime.git
- Use master for for all Juno work (3.8/4.2/4.1.1)
- Use R3_7_maintenance for 3.7.1/Indigo SR1 work


Platform UI (plus Eclipse4 UI) *
git://git.eclipse.org/gitroot/platform/eclipse.platform.ui.git

* don't use master

Development and maintenance branches for Platform UI only

Branch	Why
R4_development	All Juno related work, both 4.2 and 3.8 that doesn't include the org.eclipse.ui.workbench. For now this also includes 4.1.1 work.
R3_development	Work that needs the 3.8 org.eclipse.ui.workbench
R3_7_maintenance	Our standard maintenance branch for 3.7.1/Indigo SR1
master	Don't commit to this branch at this time

See http://wiki.eclipse.org/Platform_UI/Git_Migration#Development_and_maintenance_branches_to_use for more information.

Use the ssh://userid@xxxxxxxxxxxxxxx/gitroot/... form for read-write access.

PW

-- 
Paul Webster
Hi floor.  Make me a sammich! - GIR