Re: Moving to bzr?

[Stefan Monnier]

> Assuming we had a good repository, how would the change go? Would the
> bzr be the main repository, or just a mirror for some time?

We've had a mirror already.  "The change" means that the main repository
would be using Bzr.

> Will we maintain the current workflow and policies, where every
> developer has full write access? Will we add some kind of
> review process?

These are orthogonal, so no we wouldn't change anything in this respect.

> Is Savannah ready for the change?

Yes and no: AFAIK the Bzr support in Savannah is still in test (yes,
this is ironic, it already supports Git, Hg, Svn, Arch, but not Bzr).

OTOH we can store the Bzr branch in the Arch area (i.e. access it via
sftp://arch.sv.gnu.org/); we've used this for the Emacs.app branch
before it was merged into CVS.  And AFAIK the "in test" Bzr support
does work at least as well the the sftp approach, tho I haven't tried
it myself.

> Is there something developers should do to switch, other than just
> installing bzr and cloning the repository?

No.

>> I.e. we're just waiting for a good Bzr repository with complete tag
>> data, and with as much merge history as we can get,
> Well, is there anyone knowledgeable enough in CVS, bzr and Arch to
> lead the process?

Anybody who wants to help should get in touch with Jason,


        Stefan