(DONE) Create git repos, restricting write access to just the account used for the migration.(DONE, 11 March 2014) Announce date for migration.(DONE, approx 1h15m) Determine which branches should be migrated over (presumably all, but there might be obsolete branches) and estimate how long this will take.(DONE, though see bug 967697) Set up repos (bugzilla and bmo) on.( DONE) Write migration instructions similar to.(DONE) script to keep bzr in sync with git.(DONE) fast-export translation script to preserve bug ID metadata.The tracking bug for the migrations is bug 929685. There are a bunch of things we'll need to do to complete this.
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. We can create a new script based on this to copy changes from git to bzr. Luckily there is already a script that is currently used to do the bzr-cvs one-way mirror.
Launchpad can mirror projects from GitHub, but it is still a manual process and not at all suited for the number of branches Bugzilla uses. The bzr-git plugin looked like a good solution but in fact can't automatically pull recent changes from git and apply them to bzr. Keeping the two repos in sync, however, is a bit trickier. It just requires a bit of translation to preserve commit metadata, which git doesn't support. Users will be able to fork the project, but they will have to push to, which in turn will push the changes to GitHub.ĭoing a one-time export using bzr fast-export and git fast-import is fairly straightforward. Similarly, there will be a one-way mirror to GitHub.
Set 1 for SSL and 0 for non-SSL connection. g Įnables or disables SSL connection for the target LDAP server.
Password of the target server tree administrator. b įully Distinguished Name (FDN) of the target server tree administrator. f Įnables or disables SSL connection for the source LDAP server. Password of the source server tree administrator. a įully Distinguished Name (FDN) of the source server tree administrator.
This is an optional command.Ĭreate the file using any text editor. For example, -S 0 or -S 3 or -S 5.ĬIFS source to the target share mapping file. Secure (SSL) or non-secure (Non-SSL) connection type of the target server. Secure (SSL) or non-secure (Non-SSL) connection type of the source server.