- 🇳🇿New Zealand quietone
This was set to postponed many moons ago (14 years) with no further comment by @Wolfflow. The page has been updated many times since then. Based on that I am setting this to outdated.
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
Closed: outdated
Correction/Clarification
Used in Documentation issues for documentation problems related to servers, such as installing/configuring/debugging Apache, MySql, PostgreSQL, etc.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This was set to postponed many moons ago (14 years) with no further comment by @Wolfflow. The page has been updated many times since then. Based on that I am setting this to outdated.