Drupal considering moving to bzr or git (from CVS)

[Eric Berry]

I know the decision has basically been made, but there is a small point I'd
like to make.

There is a small feature of Bazaar which I believe plays very well with
Drupal usage. It was mentioned in one of your comments David, and is often
overlooked I think.

Bazaar supports FTP out of the box for both branching and pushing. I think
this is a key feature of bzr in regards to it's usability with websites.

As an "end-user" of drupal, I could install the Drupal files on my new host
by doing something as simple as:
[code]
bzr branch [remote drupal 8 branch] drupal_8
bzr branch drupal_8 my.domain.com
cd my.domain.com
bzr push ftp://[my remote host]/www
[/code]

I don't even need an FTP client. Now I just go through the online
instructions. The second branch into my.domain.com isn't really necessary,
but will make upgrading easier.

Upgrading:
[code]
bzr branch [remote drupal 8.x branch] drupal_8.x
cd my.domain.com
bzr merge ../drupal_8.x
bzr push ftp://[my remote host]/www
[/code]

This is nice as it will delete files which have been removed in the Drupal
8.x branch, and will only push the differences, making the upgrade quicker
and safer.

If I'm the developer of a new website and I am using bzr for my website's
other code, then I can upgrade my Drupal website, manage non-drupal parts of
my code, and push the changes live all with one tool.

Lastly, in my opinion, the FTP support makes bzr very cheap to use. I don't
know of any hosting company (even the really inexpensive ones) that can
support Drupal and doesn't offer FTP making it the ideal VCS solution for
startups. This is one of the reasons why I (myself) chose both Drupal and
Bazaar to do the few websites I've developed for people.

Just m2c.
Eric

On Sat, Feb 13, 2010 at 3:50 AM, David Strauss <david at fourkitchens.com>wrote:

> On 2010-02-13 10:15, Eugene Wee wrote:
> > Sounds like the battle is nearly lost already (webchick has "sent off
> > an official recommendation tonight to the Powers That Be and the
> > infrastructure list, so we'll find out what happens from here").
>
> That was sent to me and others. The decision still isn't final, but it's
> certainly in the "git wins unless otherwise disqualified" phase.
>
> > Of the five points cited by webchick in the conclusion, two were
> > evaluated as neutral (features and learning curve),
>
> This isn't for overall git usability. This is based on the workflow
> document each side prepared for doing two basic things:
>
>  * Creating and improving patches to core (a distributed workflow)
>  * Maintaining a module (an optionally centralized workflow)
>
> > one was evaluated as not relevant (Launchpad),
>
> Only "not relevant" in the context of moving Drupal development to our
> own Launchpad installation.
>
> > and two were evaluated as favourable to
> > git (community traction across the Internet and Drupal itself, and the
> > flow of Drupal developers and code to Github).
>
> Indeed. Drupal's decision isn't intended to be a verdict on "the best
> DVCS tool." It's a verdict on "the best DVCS tool for the Drupal
> community."
>
> > It seems that Windows
> > GUI is the only possible blocker remaining for git, but webchick
> > apparently was satisfied that it is usable for git, despite concerns
> > about the possible second class citizenship of Windows with respect to
> > git that was cited earlier in the discussion.
>
> Correct.
>
> --
> David Strauss
>   | david at fourkitchens.com
> Four Kitchens
>   | http://fourkitchens.com
>   | +1 512 454 6659 [office]
>   | +1 512 870 8453 [direct]
>
>


-- 
Learn from the past. Live in the present. Plan for the future.
11101000
http://www.townsfolkdesigns.com/blogs/elberry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20100213/a9c71b67/attachment.htm