<br><br><div><span class="gmail_quote">On 2/5/07, <b class="gmail_sendername">Greg Knaddison - GVS</b> <<a href="mailto:Greg@growingventuresolutions.com">Greg@growingventuresolutions.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 2/5/07, Khalid Baheyeldin <<a href="mailto:kb@2bits.com">kb@2bits.com</a>> wrote:<br>> Up to now, I was using CVS to track Drupal 4.7 core and modules. The new<br>> system does complicate matters, since it is quite acceptable to do:
<br>><br>> DRUPAL-5 as a branch<br>> DRUPAL-5--1-0 as a tag<br>> ... changes<br>> DRUPAL-5--1-1 as a tag<br><br>there should be a DRUPAL-5--2 branch from the same branch point as the<br>DRUPAL-5 branch before this next step:
</blockquote><div><br>I agree that would make the matter less of an issue.<br><br>However two points:<br><br>1. The new release system does not enforce a branch for the major number. I know<br>because I used tags only for a
1.1 and 2.0 and the system just accepted it.<br><br>2. There is now more overhead per module for those who check it out. A directory<br>per tag per module.<br><br>Right now I just have:<br><br>drupal/<br><br>drupal/HEAD<br>
drupal/HEAD/drupal<br>drupal/HEAD/contributions<br><br>drupal/47<br>drupal/47/drupal<br>
drupal/47/contributions<br>
<br>drupal/5<br>
drupal/5/drupal<br>
drupal/5/contributions<br>
<br></div>And that is it.<br><br>Under this scheme one has to maintain a sandbox directory for each branch of a module<br>separately.<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> ... changes<br>> DRUPAL-5--2-0 as a tag<br>><br><br>Please see my earlier post for clarification:<br><a href="http://lists.drupal.org/pipermail/development/2007-February/022380.html">http://lists.drupal.org/pipermail/development/2007-February/022380.html
</a><br><br>I'm mostly representing dww's point of view on this idea.<br><br>> If you do an update from CVS while changes are in but before the module is<br>> tagged<br>> you have the chance of getting unstable code.
<br><br>Which has always been the case with the old system. Right? The old<br>DRUPAL-4-7 branch of contrib isn't known to be stable so if you<br>updated down that you could get anything (stable, unstable, buggy,<br>
etc.).<br><br>Regards,<br>Greg<br></blockquote></div><br><br clear="all"><br>-- <br><a href="http://2bits.com">2bits.com</a><br><a href="http://2bits.com">http://2bits.com</a><br>Drupal development, customization and consulting.