The doc page:"Setting up a test environment to review patches" [#723026]

Hi All, it's about 6 months that I started to work with a Debian Linux Server and would like to start over with a Drupal Patch review activity. This also for learning more out of Drupal code and start to help out. I know a lot of posting about the discussion over CVS and the activity and testing around for migrate to a new Revision System, so my question is:

Is this page really clear to follow? Setting up a test environment to review patches

In doubt:

1. the page upper right tagging says Drupal 6.x

2. in the paragraph Retrieving a copy of Drupal HEAD from CVS it says:

cd /path/to/web/root/

which is clear to me but it's not a bit confusing?

With a clear example of a default directory like ie /var/www/ (which is the most default linux distribution location) and mentioning that other better choice for this purpose may be ............
would simplify understanding, IMO.

2. In the paragraph Testing patches for versions other than Drupal HEAD it says:

For example, to checkout a test version of Drupal 4.6.1, use the command: ....

showing an example for DRUPAL-4-6-1 drupal

This is a bit confusing me, though I know reading some of other posting and contrib modules readme.txt files that there are still developments that starts from the old Drupal 4 versions, but IMO this page should focus on Drupal 6 or even to 7 core testing efforts, this just as for gaining more Drupal passionate that would like to contribute
on the last Drupal developments, which in my opinion should be the better choice after reading: Drupal 7.0 Alpha 2 released

Please ask me if any of my sentence could led to misunderstanding (still no native English writer ;-) ).

Thanks

_{Note: I will contribute to clearer and simplify the mentioned page upon your suggestions: Thanks}

Comments

Comment #1

Wolfflow CreditAttribution: Wolfflow commented 26 February 2010 at 07:26

Some additional considerations:

The paragraph Testing patches for versions other than Drupal HEAD may be simplified so:

There are also patches in patch queue for different Drupal Branches:

When retrieving a copy of Drupal from CVS, the same checkout command is used, however a branch must be specified in order to retrieve a version of Drupal other than HEAD. A list of available branches is available from the Using CVS with branches and tags page of the Contributor's Handbook.

To checkout a test version of Drupal 4.6.1, use the command:
cvs -z9 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal checkout -r DRUPAL-4-6-1 drupal

To checkout a test version of Drupal 5.12.1, use the command:
cvs -z9 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal checkout -r DRUPAL-5-12-1 drupal

To checkout a test version of Drupal 6.14.1, use the command:
cvs -z9 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal checkout -r DRUPAL-6-14-1 drupal

Remember that the version assigned to a patch and the version of Drupal to which it is applied must match.

Note: in this example number of Drupal version may be wrong, that is just for describing my proposal of simplification.

Comment #2

Wolfflow CreditAttribution: Wolfflow commented 7 March 2010 at 14:47

I would really appreciate if you comment, evaluate my proposal for the page mentioned. Maybe did I misunderstood totally?

Comment #3

Wolfflow CreditAttribution: Wolfflow commented 16 April 2010 at 14:07

Status:

Active

» Needs review

Changing status from "active" to "needs review" after some time to accelerate for support.

Comment #4

arianek CreditAttribution: arianek commented 3 May 2010 at 00:21

Status:

Needs review

» Active

Hi Wolfflow -

There are only a few people actively working on the docs queue, and we are quite occupied with D7 docs and some major restructuring of the online docs, so thanks for your patience.

I think the suggestions you've made are good, with the following considerations:

- I'd leave the /path/to/web/root/ and then add a sentence afterward saying something like "if you are using Linux, the path is likely /var/www/.

- For the commands for checking out different versions of HEAD from cvs (and wherever else) I'd just leave out D4 altogether at this point.

I'm setting this issue back to "Active" until it gets worked on, you are more than welcome to make the edits yourself, and *then* set the issue to "needs review" so that a docs team member can review your changes.

Thanks!

Comment #5

Wolfflow CreditAttribution: Wolfflow commented 4 May 2010 at 23:54

@arianek

Thank you for your feedback! I will take action as you suggested.
Oh I know that at time all efforta are on docs for 7 so I'm worry to have patience and wait as needed.

Bye!

Comment #6

Wolfflow CreditAttribution: Wolfflow commented 20 October 2010 at 02:53

Status:

Active

» Postponed

Set to "Postponed" until I get more confident and clear with all aspect of the document for review the entire article for a rewrite to be more simple and accessible for newbies.