<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>Although I don't have much experience with either Hg or Bzr, it appears to me that bzr has more support backing its development and use; Hg just has Mozilla corp. In addition, pending what you said about the commands for bzr being almost exact in comparison to cvs, I'd have to vote for bzr. <br><br>That said however, I am neither an active contributor nor a user of either bzr or hg, so this vote can count for half :p<br><br><br><br><br>----- Original Message -----<br>From: "Max Kanat-Alexander" <mkanat@bugzilla.org><br>To: developers@bugzilla.org<br>Sent: Sunday, September 6, 2009 4:45:58 AM GMT -05:00 US/Canada Eastern<br>Subject: Re: Moving Away >From CVS: A Vote<br><br>On 09/05/2009 10:01 PM, Bill Barry wrote:<br>> I seem to recall some dirstate problem that we had to change how our<br>> server was working because we couldn't push to it. A new version came<br>> out about a week after we started evaluating bazaar and we decided to<br>> upgrade and found that we couldn't push to it. I think it was 1.13 or<br>> something like that. We gave up pretty quickly after that.<br><br> Hmm. It's possible there was a problem with dirstate that I never ran <br>into. At this point most repos are in the packs format (same as git <br>uses) and it seems to be working totally fine.<br><br>> Every release (and there has been almost 1 a month for the past 2 years)<br>> seems to fix at least a dozen bugs. How exactly does there happen to be<br>> a new bug fixed every other day on average?<br><br> I'd say that probably a lot of what's showing up there is just issues <br>found in Release Candidates. Not sure, though. I haven't encountered a <br>serious issue in bzr in a while.<br><br>> Wasn't it you that wrote the post about sucking less every release?<br><br> Hahaha, it was. :-)<br><br>> No it doesn't have bound branches; I'll give you that too. I don't think<br>> it would be that difficult to write as an extension. [snip]<br><br> Fair enough. I think bound branches is how we'd recommend users check <br>out Bugzilla code, though, so that they could do "bzr up" and it would <br>"just work" pretty nicely.<br><br> As a result of having bound branches, bzr also has "lightweight <br>checkouts", which are just a copy of the working tree without the entire <br>history, and a pointer back to the main repo for operations that require <br>the history. Of course, I've never used lightweight checkouts, and I <br>don't know anybody who does. :-)<br><br>> My bound mode extension can be found here:<br>> https://bitbucket.org/Bill_Barry/boundmode/<br><br> Cool. I will look into that if we go with Hg (though the way the voting <br>is going bzr seems pretty likely).<br><br>> It will be much easier to maintain a fork than it currently is to<br>> maintain a single giant patch. I pity what Greg has to go through each<br>> time he attempts to upgrade Testopia. That is a lot of work (which<br>> wouldn't be nearly so difficult if it was easier to keep up with the<br>> changes).<br><br> Yeah, I wouldn't want to maintain Testopia without bzr, myself, if I <br>were a maintainer. Of course, I think the "Testopia For Bugzilla 3.4" <br>may not involve a patch to Bugzilla at all. We'll see. :-)<br><br> > His latest news was a bit unsettling as far as the future for<br>> Testopia goes.<br><br> Yeah, agreed, but it's possible we'll see some community member come <br>and pick it up.<br><br> -Max<br>-- <br>http://www.everythingsolved.com/<br>Competent, Friendly Bugzilla and Perl Services. Everything Else, too.<br>-<br>To view or change your list settings, click here:<br><http://bugzilla.org/cgi-bin/mj_wwwusr?user=powellc@powelltechs.com><br></div></body></html>