[development] bzr battle plan
ber at webschuur.com
Thu Nov 24 11:11:07 UTC 2005
I "branched" upload to make it a full blown modular file system. It now lives
in CVS contribs. Recently some developers showed interest, it seems this
porject is taking off.
I think this might be an interesting testcase, because I think these useacases
is exactly what BZR is good at. If someone can hold my hand while getting
this "contrib" out of CVS and into that BZR, we have a nice place to work,
we can see how well bzr takes off. And in the end we can evaluate this.
Op donderdag 24 november 2005 11:23, schreef Dries Buytaert:
> On 24 Nov 2005, at 10:48, Karoly Negyesi wrote:
> >> I do not plan to use bzr at this point. (Please note that this is
> >> a chx-ism, and not something I approved up front.)
> > I emphasize then "eventually" and "may".
> I know. I just wanted to point out that:
> 1. I won't switch to bzr (yet), and that
> 2. bzr is not officially supported (yet).
> I actively used darcs for a couple months. It looked exciting in the
> beginning, but even after a while, I could not get used to it and I
> decided to stick with CVS. Having to adapt your workflow only to
> find out it isn't what you hoped for can be frustrating. I still use
> darcs occasionally because of a research project I'm involved in.
> Also, I know that bzr is not darcs, and that bzr has some
> functionality that is sorely missing in darcs. The point is that I'm
> somewhat reluctant to go through this again.
> That said, the bzr repository makes for an interesting experiment,
> and I understand the potential benefit of a distributed model in the
> context of Drupal (it had big impact on Linux kernel development).
> If bzr gets support within the Drupal community, we could consider
> hosting the bzr repository ourselves and actively supporting it. If
> it doesn't take off, no harm done. We'll see how it goes. :-) In
> the mean time, I'll toy with bzr a little, and keep an eye on how it
> gets used within the Drupal community.
> Hopefully that clarifies my take on this,
> Dries Buytaert :: http://www.buytaert.net/
More information about the development