[development] Is DRUPAL-5 branch necessary for module?
metzlerd at evergreen.edu
Tue Jan 23 15:56:55 UTC 2007
I recently had a discussion with Derek about the same thing, where he
convinced me that branching was the right thing to do. The current
recommended best practices would suggest that you branch once you've got
a stable 5.x compatible release, but before you start developing any new
The reason to do so is so that you can do a bug fix if you need to on
the stable code without forcing people to upgrade to potentially
unstable code to fix some bug.
From: development-bounces at drupal.org
[mailto:development-bounces at drupal.org] On Behalf Of Vernon Mauery
Sent: Tuesday, January 23, 2007 7:42 AM
To: development at drupal.org
Subject: Re: [development] Is DRUPAL-5 branch necessary for module?
I am not a CVS guru, but I think this model makes perfect sense to me
-- until HEAD is not compatible with 5.0, there is no need to branch.
But then, it sounds like that won't be too long before some major
changes are introduced to HEAD. But you still might keep your module
HEAD compatible with D5 until the D6 API (or whatever is next)
On 1/22/07, _craig <drupal-list at 2craig.com> wrote:
> Do I really need to have a separate DRUPAL-5 branch for my contributed
> module? The documentation* seems to indicate I need to. Is anything
> preventing me from just tagging files under HEAD with DRUPAL-5--1-0?
> now and in the near future I will only be making changes for 5.x so I
> see the need to have a separate branch. Of course if you look at my
> module**, it's too late...
> * http://drupal.org/handbook/cvs/quickstart#branch-tag
More information about the development