Hi, Our team uses it very successfully with quite a complex product involving 40+ sub projects (each with seperate bzr repository). We have production deployments, and we never had any bzr problems. I woud say it is definitely stable enough to use as everything is properly tested, and upgrades are managed properly i.e. stuf never breaks when upgrading to a newer version of bzr. We have a mixed team: some linux some windows+cygwin and also windows without cygwin, and I can definitely recomend it. There is a email plugin for bzr, I wonder if it is possible for it to email the lates commits (with gzipped diffs) to the people on your team, I think automaing this is important in your situation. <div>On 9/28/06, Stefan Reichör <<a href="mailto:stefan@xsteve.at">stefan@xsteve.at</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Alexander Belchenko <<a href="mailto:bialix@ukr.net">bialix@ukr.net</a>> writes:</blockquote><snip> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Is someone else using bzr on Windows? ;-) How big are your repositories and do you recommend bzr for a project now? Stefan. </blockquote></div> -- -- The source is strong in this one.