Jump to: navigation, search

Difference between revisions of "Platform-releng/Juno Git Migration Process"

m (New page: Description of the process the Equinox RT and Eclipse projects are using to migrate to git # Open a bug against the component for the migration. # Platform releng will run a test migrat...)
 
m
Line 1: Line 1:
 
Description of the process the Equinox RT and Eclipse projects are using to migrate to git
 
Description of the process the Equinox RT and Eclipse projects are using to migrate to git
  
# Open a bug against the component for the migration.   
+
# Open a bug against the component for the migration For example [https://bugs.eclipse.org/bugs/show_bug.cgi?id=353368 bug 353368 migrate platform.resources to git] This bug will be blocking the overall git migration bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=345479 bug 345479 Migrate Eclipse and Equinox projects from CVS to git]
# Platform releng will run a test migration and ask the committers to look at 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.
+
# 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.
 
# Plan a date for the actual migration
 
# Plan a date for the actual migration
 
# 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.
 
# 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.

Revision as of 11:47, 23 August 2011

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 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 tests builds
  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