MailNews:HgSwitchover

This page describes the process of switching to Hg, who's going to do what, and when.

KaiRo has done most of the changes to the build system, including setting up a test repo. See this page for the details of how to do a build using the test repository.

Before we all switch to using those instructions (using a new repo, not the one in that page), the following needs to happen:

• Announce plan to m.d.a.t, m.d.a.sm, m.d.a.c, m.d.planning (david/dmose/kairo, whenever this page is ready)
  • Dan's post

• Close CVS tree (KaiRo: Tuesday, 5AM Pacific)
  • TREE CLOSED

• Tag CVS files to import with HG_COMM_INITIAL_IMPORT (KaiRo, just before populating comm-central with that revision)

• populate new Hg repo (http://hg.mozilla.org/comm-central) with current copy of files from CVS trunk, land patches of bug 444686 there, ensure build(s) works (KaiRo, Tuesday, after the tree closes)
  • How Long: KaiRo expects 1 hour or less to get code there and apply the build system/patches so it should build.

• Get Thunderbird unit test buildbots working off of Hg (gozer)

• Get Thunderbird nightlies working off of Hg (gozer)

• Get SeaMonkey builder+nightly buildbots working off Hg (KaiRo, as soon as all code is in the repo)

• Get SeaMonkey unit test buildbots working off Hg (KaiRo, once builder+nightly boxes are spinning their first builds)

• finalise docs, comments welcome.
  • Standard8 has posted these and links to them:
  • Comm-central source code (Mercurial)
  • comm-central
  • How comm-central's build system works

• open Hg tree (who? when?) and note document updates.
  • KaiRo, davida, dmose or gozer should be able to do this from a tinderbox message aspect.

Any missing steps?