[development] bzr battle plan

[Adrian Rossouw]

My major issue with BZR is source repository browsing.

We need a central web based interface to browse the repository, and  
do diffs and the like.
Applications like this exist for both svn and cvs, but not for bzr.

There is a php library for svn that would allow us to directly  
integrate it into Drupal
(which would be great for a project management tool. Think trac in  
php, but with Drupal).

So long as the files are in one location, I'm happy .. but I really  
do think we need to
give cvs the boot. SVN is far simpler to comprehend, and script.


On 24 Nov 2005, at 8:32 AM, Karoly Negyesi wrote:

> bzr and Drupal.
>
> We now have a bzr mirror of the core. It's easier for a group of  
> people
> to work on a bigger change in their own branch and submit a final  
> diff.
> (hint. bzr diff --diff-options -F^f) Eventually, Dries may use a  
> bzr branch,
> too and then instead of patches we may submit a link to a bzr  
> branch instead
> of a patch file but this is not so important.

--
Adrian Rossouw
Drupal developer and Bryght Guy
http://drupal.org | http://bryght.com