Moving Bugzilla to git?

Gervase Markham gerv at
Tue Oct 29 13:43:29 UTC 2013

On 25/10/13 15:12, Frédéric Buclin wrote:
> Le 25. 10. 13 14:08, Gervase Markham a écrit :
>> I realise that moving to git is some work, but why do you link it to
>> upgrading to another release?
> Because the problem to upgrade to 4.4 was that it was available on bzr
> only, while 4.0 was the last branch available on CVS. So let's say that
> 4.0.11 was only available on bzr for some reason, then I would have been
> unable to upgrade from  4.0.x to 4.0.y (y > x). 

But you could upgrade from 4.0.x CVS to 4.0.x bzr, then upgrade to 4.0.y.

> If you decide to do that
> for e.g. Bugzilla 4.4 and for some reason git cannot be installed, then
> you would have the same problem, i.e. unable to upgrade from 4.4.x to
> 4.4.y. One could say I could use tarballs or diffs, but that's more work.

It seems that the underlying problem with this scenario boils down to
the "git cannot be installed" problem. As long as git can be installed
on a server, then that server should have no problem with making this
transition, even if they don't upgrade their Bugzilla at all during the
process (and that would be the recommended way anyway).

Stephanie's comments are helpful in determining whether we might have
problems with people not being able to install git. It seems unlikely...

dev-apps-bugzilla mailing list
dev-apps-bugzilla at

More information about the developers mailing list