[development] CVS branch work best practices?

Michael Favia michael at favias.org
Fri Feb 2 15:45:59 UTC 2007

Dries Buytaert wrote:
> On 02 Feb 2007, at 15:43, AjK wrote:
>> First, contrib devel is not core devel. Core devel happens at HEAD as
>> we all
>> know. But contrib need not.
> Yep, as a contrib developer you have two options: develop in HEAD or
> develop in a DRUPAL-5 branch.
>  a. For people that are OK with following core's release schedule, it is
> easier to develop in the CVS trunk/HEAD.  This means you can't release a
> significant upgrade of your module until the DRUPAL-6 branch is
> available.  In this case, your work is targeted to be released when
> Drupal 6 becomes available.  The Drupal 5 version of your module is in
> maintenance mode, just like core's DRUPAL-5 branch.

Why would the lack of a DRUPAL-6 branch preclude releasing a significant
upgrade in any way? You can always just backport your stable changeset
to the D5 branch no? This is how I worked in a traditional software
development environment for years. The D5 branch should represent a
subset of all of the patches you applied to HEAD and should apply
cleanly as a result.

> I usually recommend people to go with (a) unless they plan to go
> "faster" than Drupal core, i.e. release more major upgrades more often
> than core does.

I agree with option A as well as stated in my other email. For
reliability, and stability in the branches.

Michael Favia                   michael at favias.org
tel. 512.585.5650        http://michael.favias.org

More information about the development mailing list