The Bazaar DVCS seems to be left far behind Git and Mercurial, at least in terms of adoption and overall mindshare in the VCS space. AFAIK the only high profile projects using bzr are Ubuntu and Launchpad, both directly backed by Canonical. So I'm wondering, would it make sense for Canonical to switch to one of the other two leading contenders instead of keep allocating resources to it ? Is there any strategic advantage, technical or otherwise, in pushing Bazaar at this time and age ?
|
closed as not constructive by Jorge Castro, fluteflute, balpha♦ Oct 10 '10 at 9:09
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.
|
Bazaar fulfills the needs that Canonical had. Unless they find new needs unfilled by Bazaar it is not necessary to consider switching - they have plenty of code using bazaar which needs to be revised when switching. So, yes, if it fullfills your needs, then use it. But as always have an escape route if for some reason you MUST switch at a later time. |
|||
|
|
|
I don't use Bazaar, but when I have to - however, in the spirit of open source bazaar fits the bill. In the viewpoint of Canonical, Git and other source control tools didn't cut it for them so they produced Bazaar which suites their needs to a T. Would I like them to switch to another VCS? Sure, but it's not likely to happen - preferred source control tools are always opinionated by design and none of them are perfect. Bazaar has plenty of projects using it - Launchpad is not just one project, it's a collection of many projects - many of which utilize Bazaar as their source control. Personally I don't like Bazaar - so for the projects I interact with I export the bazaar repository to Git then import my changes back in. The majority of all modern DVCS are inter-compatible to some extent (and most are compatible with SVN and other CVCS). So in the end each project will use what is best for it's team. Each developer will use whatever is best for them. |
|||||
|
|
Sometimes, I find what VCS people use pushes away developers from contributing for small fixes since they aren't familiar with the particular VCS. It may not be true, but it has happened to be multiple times, where I want to contribute, but dont want to go through the hassle of trying to setup and use a new VCS. They would definitely be helped if they were to switch to a more widely used VCS, but if the one they are currently using fulfills all their needs i dont see them switching. :) |
|||||||
|