Bugzilla:Migrating to git: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 26: Line 26:


It was originally proposed to keep the bzr repo going for only another 9 months, but it was also suggested that we keep it running until all current versions (up to 4.4) are EOLed, since the suggested upgrade path is to pull changes directly from the repo, rather than applying a tarball or diff.  However, we do publish tarballs and diffs, so this is about convenience in upgrades, since it is always possible to upgrade via tarball or diff.
It was originally proposed to keep the bzr repo going for only another 9 months, but it was also suggested that we keep it running until all current versions (up to 4.4) are EOLed, since the suggested upgrade path is to pull changes directly from the repo, rather than applying a tarball or diff.  However, we do publish tarballs and diffs, so this is about convenience in upgrades, since it is always possible to upgrade via tarball or diff.
== Plan ==
There are a bunch of things we'll need to do to complete this.  Some can be done in parallel.
Pre-migration:
# fast-export translation script to preserve bug ID metadata.
# git2bzr script to keep bzr in sync with git.
# Write migration instructions similar to https://wiki.mozilla.org/Bugzilla:Moving_From_CVS_To_Bazaar
# Set up repos (bugzilla and bmo) on git.mozilla.org.
# Set up repos on GitHub and configure git.m.o repos to mirror there.
# Determine which branches should be migrated over (presumably all, but there might be obsolete branches) and estimate how long this will take.
# Announce date for migration.
Migration:
# Disallow commits to bzr aside from those originating from the git2bzr script.
# Perform fast-import/-export migration on all (supported) branches of bugzilla and bmo.
Confirmed users
1,927

edits