[development] Is DRUPAL-5 branch necessary for module?

[Metzler, David]

I've been corrected on this assumption before.  Just because you create a branch for DRUPAL-5 doesn't mean you've agreed to do any commits to it, or port any new features to it.  Think of it as insurance.  You can still do all your development in HEAD and then branch from it when you need to make a new 5.x release .   If you ever do.  You may never need it, but if you get a critical bug that need's fixing while in the middle of making radical changes in HEAD, you (and your project users) will be glad that you had the DRUPAL-5 branch to make that fix in. In the meantime, blissfully put all your new features in head and when you get a new major release, branch and tag, baby! 

See Derek, I really did drink the KoolAide. 

Dave

-----Original Message-----
From: development-bounces at drupal.org on behalf of andrew morton
Sent: Tue 1/23/2007 09:54
To: development at drupal.org
Subject: Re: [development] Is DRUPAL-5 branch necessary for module?
 
On 1/23/07, drupaladmin at misterwhipple.com <drupaladmin at misterwhipple.com> wrote:
> But, why bother updating HEAD at all? If a module has no Drupal 6
> development going on, can't all updates be made just to DRUPAL-5, and HEAD
> ignored? I got the impression that single-Drupal-version development of a
> module could confine all its updates to the one branch..
>
> If someone tells CVS "give me the DRUPAL-5 branch", they'll always get the
> latest thing in that branch unless they specify a release tag, right?

Yeah, but then if you've put in lots of fixes on the DRUPAL-5 branch
you'll have to pull them up to HEAD before you start working on
updating your module for Drupal 6. And it's usually a little while
before a Drupal 5 compatible module stops working with the next
version. It's not really not a huge issue but it is an annoyance.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 3887 bytes
Desc: not available
Url : http://lists.drupal.org/pipermail/development/attachments/20070124/ae9ad41f/attachment.bin