<br><br><div><span class="gmail_quote">On 2/5/07, <b class="gmail_sendername">Gerhard Killesreiter</b> <<a href="mailto:gerhard@killesreiter.de">gerhard@killesreiter.de</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;">
Adrian Simmons wrote:<br>> Gerhard Killesreiter wrote:<br>>> Yeah, this is a somewhat annoying point about the new release system.<br><br>> Such was my suspicion. The whole cvs export > svk import vendor branch
<br>> etc has been great for speeding up site updates to my multisite install.<br>> This inability to track the latest stable branch will slow me down. Such<br>> is life :)</blockquote><div><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>... changes<br>DRUPAL-5--2-0 as a tag
<br><br>If you do an update from CVS while changes are in but before the module is tagged<br>you have the chance of getting unstable code.<br><br><br></div>I think we need to think of a way to accommodate developers. It may be just
<br>a bunch of How To documents that organize the thoughts mentioned in this<br>thread.<br><br>There is also this that hit CVS a few hours ago:<br>
<a href="http://drupal.org/project/module_installer">http://drupal.org/project/module_installer</a><br>
But it is for end users, not developers who want to maintain patched versions.<br>
<br></div>-- <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.