Moving Bugzilla to git?

Stephanie Daugherty sdaugherty at
Wed Oct 30 14:35:15 UTC 2013

The pain points of moving from cvs or svn to anything else largely don't
exist for this conversion, because git, hg, and bzr are all at similar
levels of functionality and interoperability to allow near
interchangeability of tools, and common subsets of operations which can be
performed across different repositories (push, pull, commit, merge, branch,
tag, etc) using the cross-protocol support of each tool. (git can pretend a
bzr repository is a git repository, bzr can pretent a git repository is a
bzr repository, etc).

My understanding is that the git-bzr integration is at a level sufficient
to support a mirror suitable for nearly all upgrade/deployment scenarios,
and the needs of many developers (history, tags and branches are 1:1 the
same, submodules and certian metadata, like linkages to bug databases may
not be). This support is also bidirectional, so it's technically possible
to move in the other direction or even both directions at the same time,
and to merge freely between the two systems, rather than being an all or
nothing, one time conversion,

This seems to be good enough that post-conversion, it would be possible to
keep the bzr repositories up, while shifting development to git as of the
time of transition, and continuing to mirror git to bzr without any
technical limitations forcing an arbitrary cutoff point.

On Wed, Oct 30, 2013 at 9:51 AM, Gervase Markham <gerv at> wrote:

> On 29/10/13 18:58, Frédéric Buclin wrote:
> > This clearly shows that you don't maintain any real Bugzilla
> > installation.
> Actually, I do.
> > "Install git, move from bzr to git, then upgrade your
> > Bugzilla to get security fixes" is extra work which not all admins are
> > ready to do.
> It would be wise for admins to do the "Install git, move from bzr to
> git" part before they needed to get a security fix...
> > This is maybe fine for developers, but certainly not for
> > all admins. If you are happy with git, feel free to use it to maintain
> > your Bugzilla installation, but this shouldn't affect installations
> > already using bzr to get security fixes.
> I guess this is one for justdave:
> "Is it reasonable to require Bugzilla administrators to switch SCM
> system on an occasion other than a release upgrade?"
> If the answer is yes, we can shut down bzr fairly soon. If the answer is
> no, we need to maintain it until all current branches are EOLed.
> Gerv
> _______________________________________________
> dev-apps-bugzilla mailing list
> dev-apps-bugzilla at
> -
> To view or change your list settings, click here:
dev-apps-bugzilla mailing list
dev-apps-bugzilla at

More information about the developers mailing list