Community
Participate
Working Groups
STEM Project SVN -> Git Migration Plan Over approximately 4 weeks in April, we wish to migrate STEM from Subversion to Git. Our plan involves splitting our existing SVN repository into multiple Git repositories and doing an import. * Timeline * - March 21: Initial discussion on committer call re/ moving to Git (complete) - March 28: Further discussion on committer call re/ moving to Git. Committer motion to develop migration plan and initiate process passes. Most committers have experience with Git. - March 29: Request Git migration from Eclipse Webmaster (this bug created) - April 2: Public announcement with STEM 2.0 milestone 1 - April: test runs of repository split and import, prepare infrastructure (build scripts, CI server, project sets, etc) and update documentation - (Tentative) April 30: Freeze SVN, execute import, roll out new Git repositories - (Tenative) May 1: Declare migration complete ** the final roll-out dates may be moved up or back in response to feedback from developers relating to the process, including any complications (or lack thereof). * Repository Layout * Currently we store rather large amounts of "denominator" data in our single SVN repository, which makes for a huge checkout (> 2 GB). We plan to split our repositories between the main code base and different types of data sets. Proposed repository layout: - org.eclipse.stem.git - Primary code base, including core and epidemiological modeling components. * Includes SVN roots of /analysis, /core, /distributed, /features, /modelgen, /models, /releng, /tests - org.eclipse.stem.data.git - Primary and common denominator data that is shipped with the STEM application. * Includes SVN roots of /data/geography, /data/population - org.eclipse.stem.data.earthscience.git - Second denominator data, not included in our binary application (published on update site) * Includes SVN root of /data/earthscience - Future repositories may be created to support new data sets as they are received. STEM did a logical refactoring a couple years ago and don't plan to restructure our repository layout (other than splitting off the 2 data roots). We don't believe our code size and history necessitates a repository split at the component level. * Process * We need the Webmaster to allocate the directory on git.eclipse.org. We will create the repositories and handle the technical SVN -> Git import, unless Webmaster prefers to. We will follow the steps as listed at http://wiki.eclipse.org/Git/Migrating_to_Git#Using_svn2git_on_a_remote_server and push back to the Eclipse Git server. One committer may be unable to use Git over SSH for push, thus requiring Git over HTTPS. However, we will ask they test both the primary and proxy methods before requesting this access.
After a test runs of svn2git, our estimated repository sizes are: 239M org.eclipse.stem.data.earthscience.git 54M org.eclipse.stem.data.git 56M org.eclipse.stem.git
I've created /gitroot/stem for you. -M.
Thanks! I rsync'ed our test run repositories to git.eclipse.org. Could you check for us that they are created and uploaded correctly? When we do our final migration later this month, we'll delete the test repositories and replace them with the final fork from SVN if that's ok?
I am a STEM committer working at the Federal Institute for Risk Assessment in Germany. I tried to connect to an example Eclipse Git repository from my computer. Only http and https are working, git and ssh are blocked by the firewall. Working: git clone http://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git git clone https://droy@git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git Not Working: git clone git://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git git clone ssh://droy@git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git git clone ssh://droy@proxy.eclipse.org:443/gitroot/cdt/org.eclipse.cdt.git Could you make https available?
I've enabled HTTPS so you should now be able to checkout/checkin via: https://committerid@git.eclipse.org/gitroot/stem/reponame.git. -M.
We're performing our Git migration today. You can change our SVN repository to read-only at your convenience. Last substantive commit is rev 3732. Tag representing fork point is rev 3733.
I've marked the SVN data as read only. -M.
Migration complete. Thanks for your assistance.
