• This week I’ve been working on vcs2vcs
• I’ve set my OS X 10.4 Tiger iMac to act as both a git server and log repository
• I have a local development version of the mozharness vcs2vcs code, where I have configured a conversion job to run taking https://hg.mozilla.org/build/puppet/ and converting it to a git repository, then publishing to my imac, together with the logs
• For the email portion, I have a local ssh tunnel running to vcssync1.srv.releng.usw2.mozilla.com:25 in order to run the email reports
• I’ve adapted the email reporting to only go to me, of course
• I’m currently troubleshooting issues as I hit them
• The process runs from beginning to end, including sending email notifications, and I hope to resolve any outstanding conversion issues in the next day or two

That is the current status: now a bit about the strategy:

• I have looked through all Hal’s bash scripts and config files to understand how the legacy vcs2vcs code is working, and have local versions checked out, and have read Hal’s documentation
• I have the mozharness vcs code also checked out, and have read through all the code and configs, and have read Aki’s documentation
• I hope to set up all the config for the build repos by next week, and have a working environment that is converting/pushing them to my local (imac) git server in time for my next 1x1 after this one
• When the conversion jobs are ready, I will coordinate with our team about the rollout. Impact is *very* low - worse case is that github build/* repos lag behind hg repos while the rollout occurs.
• After having experience with build/* repos, will have a better idea of end-to-end process and impact of migrating from legacy to new vcs conversion process, and will use this information to plan coordination of other repos with relevant parties (IT, sheriffs, relops, our team, devs, …)

http://petemoore.tumblr.com/post/75048061079