Platform-releng/Juno Git Migration Process

From Eclipsepedia

Jump to: navigation, search

Description of the process the Equinox RT and Eclipse projects are using to migrate to Git

  1. Open a bug against the component for the migration For example bug 353368 migrate platform.resources to git This bug will be blocking the overall Git migration bug 345479 Migrate Eclipse and Equinox projects from CVS to git
  2. Platform releng will run a test migration and ask the committers to inspect the test repository and update the bug with any changes that need to be made during the actual migration. For instance, some projects have asked that their bundles be reorganized into different subdirectories in Git versus CVS.
  3. Plan a date for the actual migration
  4. Advise on the appropriate developer mailing list the date for the migration so the committers on that team are aware that the CVS repository should not be updated during that time.
  5. Migration proceeds and bug is updated with location of new git repository.
  6. Update the map files for the migrated bundles in HEAD and R3_7_maintenance branches of org.eclipse.releng so we can run test builds (Hudson job for test builds is here login with your committer credentials.
  7. Send another note to the mailing list advising that the migration is complete and all future development should proceed in Git
  8. Update wiki documentation etc. to reflect the new Git repo locations of source code