Bzr development stopped

[Philippe Lhoste]

On 29/11/2012 22:11, Carlos Mundi wrote:
> Thanks for all your work.  I no longer watch this list, but I maintain private
> communication with Martitza and a few other ex-bzr users who used to hang out here but
> have moved on.  We have all accepted git.  I sadly migrated my last bzr repo to git at the
> end of summer.

I am currently learning Git myself, and I admit that it has some good things (in-place 
branches, good support of non-English file names) and some less good ones (renaming, 
although not as bad as it seems, and management of empty dirs).

> So I hope someone will apply what was learned here to git, which still lags in the GUI
> area.  Sorry, TortoiseGit has improved much but is still not as good as Bazaar Explorer in
> concept or execution, and obviously it is Windows only And not all of us want to use
> GitHub or struggle with Gitoruous.  On the other hand, GitBlit shows a lot of promise and
> could benefit from the Bazaar Explorer experience.

I never liked the TortoiseXxx GUIs, partly because of bad experience on the old computer I 
had at the time: it slowed down a lot the system. I admit I haven't tried again on the 
more modern computer I have now.

Indeed, Bazaar Explorer is a fine software, well made and nice to use.

Being a GUI man (at ease with command line, but working faster with GUI for most 
operations), I tried some GUIs for Git and found out that Git Extensions is nice, quite 
well made, and relatively complete in its support of Git options. Now, I only used briefly.

I am a Windows user, and I avoided Git partly because of its bad Windows support at the 
time, and partly because of its reputation of complexity of use.

Today, Windows support is very good, and reading the ProGit book, I find the ideas 
relatively clear and logical (again, at a superficial level, yet).

I still appreciate Bazaar that served me well for years, although at a primitive level: I 
never practically used branches, not liking the idea of spreading directories everywhere.
I appreciated the flexibility of the workflows and the quality of the documentation, but 
my confused mind failed to understand when to use lightweight or heavyweight checkouts, 
the difference between pull and merge, and the various user cases explained in this list...

I had to use Git to collaborate on a project (a French book on Lua), and found out it 
wasn't as frightening, I even appreciated the suggestions it makes when doing operations 
like git status or similar (Bazaar does that too, but less systematically).

I am not somebody that like to follow the mass for the sake of it, but I find enough 
qualities and advantages of using Git to switch my repositories to it, once I feel 
comfortable enough.

-- 
Philippe Lhoste
--  (near) Paris -- France
--  http://Phi.Lho.free.fr
--  --  --  --  --  --  --  --  --  --  --  --  --  --