Stub issue for discussing reorganisation of the contributing/support handbook. This is for testing. Overall issue queue etiquette and submission of patches is elsewhere.

# Testing

* What code to test

* Applying patches

* How to test and report findings

Comments

add1sun’s picture

add1sun commented

We have 2 Reviewing patches pages currently - obviously needs some consolidation:

http://drupal.org/node/283840
http://drupal.org/patch/review

Then there is:
Applying patches: http://drupal.org/patch/apply
Patch spotlight: http://drupal.org/patch/spotlight

catch’s picture

catch
he/him
Primary language English
commented

Damn, I looked everywhere but /patch/review when checking for existing pages :(

I'll have a go at merging 283840 into it later on.

Anonymous’s picture

Anonymous (not verified) commented
Component: Misc » New documentation
add1sun’s picture

add1sun commented
Status: Active » Reviewed & tested by the community

Hm, so seems like we pretty much have what we need in:

Reviewing patches: http://drupal.org/patch/review
Applying patches: http://drupal.org/patch/apply
Patch spotlight: http://drupal.org/patch/spotlight

add1sun’s picture

add1sun commented
Title: Contrib Redesign: Testing » Getting Involved: Testing section work
Status: Reviewed & tested by the community » Needs work

Created a new landing page that needs to be written. http://drupal.org/node/314199 We have other ways for people to help with testing too. Moved Reviewing patches, Setting up dev env for review and Patch spotlight here. I didn't move Applying patches because that is something folks need to do/have access to outside of helping with testing.

MGParisi’s picture

MGParisi commented
Version: » 6.x-1.x-dev
Status: Needs work » Fixed

This looks good, and will be redefined as per another open item that I am working on to combined/mix/fix all of this into a better site map... will have to wait till the IA person comes!

Marked as Fixed because these issues will be addressed as we do a redesign of this section

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.