Greg, Ryan, and Documentors,<br><br>After reading Ryan and Greg's responses, the solution seems obvious... the page shouldn't make <i>any</i> assumptions or determine priorities for use-cases. It should be verbose with sections clearly labeled.<br>
<br>-- this is <i>how</i> you check out HEAD and this is <i>why</i> you'd want to check out HEAD<br>-- this is <i>how</i> you check out a specific version and this is <i>why</i> you'd want to check out a specific version<br>
<br>Greg wrote:<br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">The only drawback I can think of for doing that is it will require us to update that page whenever a new version is released.<br>
</blockquote>
<br>I think as long as it is clear that the text you are providing as a sample is a variable (replace "Drupal-6-6" with the most recent stable release.").<br><br><b>Point of clarification needed:</b><br>Greg, what you wrote makes me ask a further clarification. It has been my experience that if you specify "DRUPAL-6" you'll get HEAD for Drupal 6. In order to get the most recent stable release of Drupal 6, you'd have to specify like this: DRUPAL-6-6.<br>
<br>Since D-6 is not under active development, it is true that the differences between the latest stable release and HEAD will be minimal. However,it is still better to use the stable release rather than HEAD, in my opinion. My experience has been that if I checkout "DRUPAL-6" --- the admin pages, update status etc. will show the version as "6.7" when the latest stable release is 6.6. I find that disconcerting. Also, I don't know how Update Status would respond when 6.7 actually does get released.<br>
<br>Greg -- am I missing something here?<br><br><b>Another Point of clarification needed:</b><br>The docs page in question mentions that there might be times when you'd want to check out a release of Drupal (presumably HEAD) for a <i>specific date</i>. It mentions no use-case. This is my guess: you are testing a patch and the patch command requires that it be applied to the precise version that the patch was created against. Given the sometimes slow work of volunteers, it can easily happen that new versions of HEAD are created before folks have had a chance to test a patch. Instead of requiring the patch-creater to keep rolling against a new HEAD, testers can simply patch against a precise version of HEAD that existed in the past. <b>Please confirm (or reject) that I've got the use-case correct here.</b><br>
<br>Thanks much,<br><br>Shai<br><br><div class="gmail_quote">On Wed, Nov 19, 2008 at 7:04 PM, Greg Knaddison - GVS <span dir="ltr"><<a href="mailto:Greg@growingventuresolutions.com">Greg@growingventuresolutions.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Wed, Nov 19, 2008 at 4:47 PM, Ryan Cross <<a href="mailto:drupal@ryancross.com">drupal@ryancross.com</a>> wrote:<br>
> Disagree.<br>
<div class="Ih2E3d"><br>
Disagree.<br>
<br>
><br>
> it is very standard practice for people jumping into a new open source<br>
> project to want to see HEAD (or trunk or whatever) or for people's first<br>
> interest in CVS is to see "what's coming". Most people that are interested<br>
> in checking out a specific version (like a stable version) are more advanced<br>
> or experienced with CVS already. Someone's first jump into CVS is not going<br>
> to be doing so in an effort to make upgrading easier.<br>
<br>
</div>Maybe, but this is Drupal. The installer in Drupal7 gets completely<br>
broken on a pretty regular basis, and that's not a new thing - things<br>
like that often happen in HEAD. I agreed with Shai's proposal. I<br>
think it should primarily explain how to check out DRUPAL-6. The only<br>
drawback I can think of for doing that is it will require us to update<br>
that page whenever a new version is released.<br>
<br>
Regards,<br>
<font color="#888888">Greg<br>
</font><div><div></div><div class="Wj3C7c">--<br>
Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank">http://drupal.org/project/issues/documentation/</a><br>
List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank">http://lists.drupal.org/pipermail/documentation/</a><br>
</div></div></blockquote></div><br>