Steve,<br><br>Yes, you've summarized exactly what I intend to do.<br><br>Shai<br><br><div class="gmail_quote">On Thu, Nov 20, 2008 at 3:43 PM, Steven Peck <span dir="ltr"><<a href="mailto:sepeck@gmail.com">sepeck@gmail.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;">Why not add all three use cases and examples? One for the HEAD<br>
version of a release (Drupal 6) and another for a specific version<br>
(Drupal 6.6) with the use cases you've just outlined?<br>
<br>
That gives three use cases and examples<br>
<br>
Development on the next generation<br>
Drupal 7<br>
<br>
Testing/bug fix on existing mainline stable branches (which is still<br>
ongoing - see bug tracker)<br>
Drupal 6 HEAD<br>
<br>
CVS Pull of current production release for whatever<br>
Drupal 6-6<br>
<br>
These are not uncommon use case scenarios in our community and it does<br>
no harm for people to be introduced and grow accustomed to such things<br>
they may not have encountered before.<br>
<font color="#888888"><br>
Steven<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
On Wed, Nov 19, 2008 at 5:11 PM, Shai Gluskin <<a href="mailto:shai@content2zero.com">shai@content2zero.com</a>> wrote:<br>
> Greg, Ryan, and Documentors,<br>
><br>
> After reading Ryan and Greg's responses, the solution seems obvious... the<br>
> page shouldn't make any assumptions or determine priorities for use-cases.<br>
> It should be verbose with sections clearly labeled.<br>
><br>
> -- this is how you check out HEAD and this is why you'd want to check out<br>
> HEAD<br>
> -- this is how you check out a specific version and this is why you'd want<br>
> to check out a specific version<br>
><br>
> Greg wrote:<br>
>><br>
>> The only drawback I can think of for doing that is it will require us to<br>
>> update that page whenever a new version is released.<br>
><br>
> I think as long as it is clear that the text you are providing as a sample<br>
> is a variable (replace "Drupal-6-6" with the most recent stable release.").<br>
><br>
> Point of clarification needed:<br>
> Greg, what you wrote makes me ask a further clarification. It has been my<br>
> experience that if you specify "DRUPAL-6" you'll get HEAD for Drupal 6. In<br>
> order to get the most recent stable release of Drupal 6, you'd have to<br>
> specify like this: DRUPAL-6-6.<br>
><br>
> Since D-6 is not under active development, it is true that the differences<br>
> between the latest stable release and HEAD will be minimal. However,it is<br>
> still better to use the stable release rather than HEAD, in my opinion. My<br>
> experience has been that if I checkout "DRUPAL-6" --- the admin pages,<br>
> update status etc. will show the version as "6.7" when the latest stable<br>
> release is 6.6. I find that disconcerting. Also, I don't know how Update<br>
> Status would respond when 6.7 actually does get released.<br>
><br>
> Greg -- am I missing something here?<br>
><br>
> Another Point of clarification needed:<br>
> The docs page in question mentions that there might be times when you'd want<br>
> to check out a release of Drupal (presumably HEAD) for a specific date. It<br>
> mentions no use-case. This is my guess: you are testing a patch and the<br>
> patch command requires that it be applied to the precise version that the<br>
> patch was created against. Given the sometimes slow work of volunteers, it<br>
> can easily happen that new versions of HEAD are created before folks have<br>
> had a chance to test a patch. Instead of requiring the patch-creater to keep<br>
> rolling against a new HEAD, testers can simply patch against a precise<br>
> version of HEAD that existed in the past. Please confirm (or reject) that<br>
> I've got the use-case correct here.<br>
><br>
> Thanks much,<br>
><br>
> Shai<br>
><br>
> On Wed, Nov 19, 2008 at 7:04 PM, Greg Knaddison - GVS<br>
> <<a href="mailto:Greg@growingventuresolutions.com">Greg@growingventuresolutions.com</a>> wrote:<br>
>><br>
>> 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>
>><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<br>
>> > interested<br>
>> > in checking out a specific version (like a stable version) are more<br>
>> > advanced<br>
>> > or experienced with CVS already. Someone's first jump into CVS is not<br>
>> > going<br>
>> > to be doing so in an effort to make upgrading easier.<br>
>><br>
>> 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>
>> Greg<br>
>> --<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>
><br>
><br>
> --<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>
><br>
--<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>