It's funny, we moved from Bzr to Mercurial within the past 4-5 months for 4 
simple reasons:

1. Speed, Mercurial was much faster than Bazaar.
2. Mercurial's workflow was more natural (I'm sure we could have changed 
Bazaar's default options via switches, but Mercurial by default was perfect)
3. Bazaar's release schedule at the time was not on a steady deployment 
cycle (at least published and their website had a lot of old information / 
references which made it appear to lack an organized development direction)
4. TortoiseBzr was much further behind than TortoiseHg and due to #3, I 
couldn't gauge when it would catch up or provide the features that Hg did.  

It's hard enough to focus on your primary development projects and cycles, 
let alone trying to determine when your version control solution was going 
to be up to speed and offer the stability that you needed.  Most of Bazaar's 
releases during our brief time using it were mostly internal, optimizations, 
structure changes, etc.  It seemed like they were still trying to figure out 
where they wanted to take it whereas Mercurial already knew it, along with 
TortoiseHg.  

I might be completely wrong, but this was based on our brief exposure to 
Bzr.  I'll have to admit that we started with Mercurial long before that, 
switched to Bzr because they "seemed" like they were further along and 
putting builds out faster.  Of course then it was more apparent to me that 
the reason for the more frequent builds/releases was because they had a lot 
of issues that they were working through.

Thanks,
George


George Peters
LYNX Technologies, LLC


-----Original Message-----
From: Mark Hammond <skippy.hamm...@gmail.com>
To: Adrian Buehlmann <adr...@cadifra.com>
Cc: tortoisehg-discuss@lists.sourceforge.net
Date: Mon, 07 Dec 2009 12:49:14 +1100
Subject: Re: [thg] [thg-dev] End of life for overlay icons

> On 4/12/2009 9:13 PM, Adrian Buehlmann wrote:
> 
> > Maybe I should extract the currently hard coded cmenu config out of
> the code
> > into a file that is read by the shell extension on init while I'm at
> it (would
> > contain the ui strings, icon file names and the exact command line
> that is
> > started).
> >
> > (Sigh, looks like quite a bit of yet more unpaid work).
> 
> Has any more thought been given to moving to something closer to bzr's 
> tortoise environment as discussed here earlier this year?  Bzr has made
> alot of progress over the last year and has resolved some long standing
> integration issues - they even recently made changes to it can be built
> with the free version of MSVC.
> 
> This would seem to solve the problem of hard-coded menu items and make 
> the more complex bits of this easier to maintain - as little written in
> C as possible, potential for code (and therefore debugging and 
> maintenance) to be shared with other similar projects, all menus etc 
> being handled by the Python implemented taskbar process, etc...
> 
> While I haven't looked at their code in about a year, I do see evidence
> (via bugs being closed) of it progressing well...
> 
> Cheers,
> 
> Mark
> 
> -----------------------------------------------------------------------
> -------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing. 
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Tortoisehg-discuss mailing list
> Tortoisehg-discuss@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
> 




------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Tortoisehg-discuss mailing list
Tortoisehg-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss

Reply via email to