[development] CVS branch work best practices?

AjK drupal at f2s.com
Fri Feb 2 16:14:13 UTC 2007


Not quite. HEAD must always exist. As Michael pointed out in another post,
one would normally do all new work in HEAD and backport. It's just another
way of working with branches and you have to decide which method is most
comfortable for you to get the job done. And even in my method, if HEAD
didn't exist where would you begin code freeze update work. The DRUPAL-6
branch won't exist until release time. You need somewhere to work before
that (unless you plan on having tardy modules then who cares ;)

  -----Original Message-----
  From: development-bounces at drupal.org
[mailto:development-bounces at drupal.org]On Behalf Of Chad Phillips --
Apartment Lines
  Sent: 02 February 2007 16:09
  To: development at drupal.org
  Subject: Re: [development] CVS branch work best practices?

  AjK wrote:

    Now, in HEAD, I start porting to DRUPAL CORE HEAD. There's no point

    features here as we are probably in code freeze anyway and we're all

    upgrading like mad.

    Then, DRUPAL-6 comes along. Branch my module, wipe HEAD (till next code

    freeze) and continue devel down the DRUPAL-6 branch.

  please correct me if i'm wrong, but given this approach, why ever have
HEAD at all?

  let's say you permanently wipe the files in HEAD except for the README.
couldn't you just create the DRUPAL-6 branch directly from the latest
DRUPAL-5 work? it doesn't seem like HEAD ever needs to exist in this model,
except as a placeholder for the README.

  am i off base??


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20070202/cea7d1f1/attachment.htm 

More information about the development mailing list