« Return to Thread: should we use bazaar?
Re: should we use bazaar?
by Jim White
::
Rate this Message:
Jochen Theodorou wrote:
> Jim White schrieb:
> [...]
>
>> From my post in this thread last week:
>>
>> One of the interesting syncing tools is hgsvn which lets you use Hg on
>> SVN checkouts. That solves your disconnected operation case and
>> allows a thorough evaluation of Hg before making the switch for the
>> central repository.
>>
>> That of course is one the essential virtues of distributed version
>> control. And naturally even more useful in the future will be
>> cross-DVCS synchronization so that this issure will become moot.
>>
>> http://cheeseshop.python.org/pypi/hgsvn
>
> it is possible with all thre of them I think... but I personally think,
> that because Bazaar has an API and git is "only" a commandline tool,
> that bazaar is better than git.. don't know about Mecurial.
I think Mercurial is probably better than Bazaar.
A repost of what I said last week:
Jochen Theodorou wrote:
> ...
> (3) can explain why another tool is better
I haven't done a direct comparison myself, but my impression so far is
that Mercurial is probably a better choice than Bazaar.
If you consider that projects like OpenJDK, IcedTea, NetBeans, and
OpenSolaris have found it the current best choice for distributed
version control, then I'm sure you'd agree that at this point
alternatives would need to explain why they're better.
http://www.selenic.com/mercurial/wiki/index.cgi/ProjectsUsingMercurial
There is SVN-to-Hg conversion available, as well as SVN-and-Hg sync.
http://www.selenic.com/mercurial/wiki/index.cgi/RepositoryConversion
One of the interesting syncing tools is hgsvn which lets you use Hg on
SVN checkouts. That solves your disconnected operation case and allows
a thorough evaluation of Hg before making the switch for the central
repository.
That of course is one the essential virtues of distributed version
control. And naturally even more useful in the future will be
cross-DVCS synchronization so that this issure will become moot.
http://cheeseshop.python.org/pypi/hgsvn
Some DVCS comparison articles:
http://www.dribin.org/dave/blog/archives/2007/12/28/dvcs/
http://www.opensolaris.org/os/community/tools/scm/
"Why Java picked Mercurial for source control" interview with Gosling:
http://www.builderau.com.au/video/play/22447748
http://bazaar-vcs.org/BzrVsHg
http://www.selenic.com/mercurial/wiki/index.cgi/BzrVsHg
http://www.selenic.com/mercurial/wiki/index.cgi/Bazaar
My best current thought it is too early for a project like Groovy to be
concerned about switching to DVCS. Developers who want to use DVCS
should use SVN-and-DVCS-of-personal-choice-synchronization over the next
year or so. Then the tools will then be more mature and the value of
switching (if any) will be clear.
Jim
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
> Jim White schrieb:
> [...]
>
>> From my post in this thread last week:
>>
>> One of the interesting syncing tools is hgsvn which lets you use Hg on
>> SVN checkouts. That solves your disconnected operation case and
>> allows a thorough evaluation of Hg before making the switch for the
>> central repository.
>>
>> That of course is one the essential virtues of distributed version
>> control. And naturally even more useful in the future will be
>> cross-DVCS synchronization so that this issure will become moot.
>>
>> http://cheeseshop.python.org/pypi/hgsvn
>
> it is possible with all thre of them I think... but I personally think,
> that because Bazaar has an API and git is "only" a commandline tool,
> that bazaar is better than git.. don't know about Mecurial.
I think Mercurial is probably better than Bazaar.
A repost of what I said last week:
Jochen Theodorou wrote:
> ...
> (3) can explain why another tool is better
I haven't done a direct comparison myself, but my impression so far is
that Mercurial is probably a better choice than Bazaar.
If you consider that projects like OpenJDK, IcedTea, NetBeans, and
OpenSolaris have found it the current best choice for distributed
version control, then I'm sure you'd agree that at this point
alternatives would need to explain why they're better.
http://www.selenic.com/mercurial/wiki/index.cgi/ProjectsUsingMercurial
There is SVN-to-Hg conversion available, as well as SVN-and-Hg sync.
http://www.selenic.com/mercurial/wiki/index.cgi/RepositoryConversion
One of the interesting syncing tools is hgsvn which lets you use Hg on
SVN checkouts. That solves your disconnected operation case and allows
a thorough evaluation of Hg before making the switch for the central
repository.
That of course is one the essential virtues of distributed version
control. And naturally even more useful in the future will be
cross-DVCS synchronization so that this issure will become moot.
http://cheeseshop.python.org/pypi/hgsvn
Some DVCS comparison articles:
http://www.dribin.org/dave/blog/archives/2007/12/28/dvcs/
http://www.opensolaris.org/os/community/tools/scm/
"Why Java picked Mercurial for source control" interview with Gosling:
http://www.builderau.com.au/video/play/22447748
http://bazaar-vcs.org/BzrVsHg
http://www.selenic.com/mercurial/wiki/index.cgi/BzrVsHg
http://www.selenic.com/mercurial/wiki/index.cgi/Bazaar
My best current thought it is too early for a project like Groovy to be
concerned about switching to DVCS. Developers who want to use DVCS
should use SVN-and-DVCS-of-personal-choice-synchronization over the next
year or so. Then the tools will then be more mature and the value of
switching (if any) will be clear.
Jim
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
« Return to Thread: should we use bazaar?
| Free embeddable forum powered by Nabble | Forum Help |
