couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Couchdb Wiki] Update of "How_to_contribute_(for_Non-Committers)" by LenaHerrmann
Date Sat, 23 Jan 2010 12:57:39 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The "How_to_contribute_(for_Non-Committers)" page has been changed by LenaHerrmann.
The comment on this change is: Added link to testing instructions.
http://wiki.apache.org/couchdb/How_to_contribute_%28for_Non-Committers%29?action=diff&rev1=6&rev2=7

--------------------------------------------------

  In this document:
   * [[#pre|Prerequisites]]
   * [[#step1|Step 1: See if your bug/feature exists in JIRA]] 
+  * [[#step2|Step 2: Run the tests]]
-  * [[#step2|Step 2: Go forth and code!]]
+  * [[#step2|Step 3: Go forth and code!]]
-  * [[#step3|Step 3: Create and Upload a Patch]]
+  * [[#step3|Step 4: Create and Upload a Patch]]
   * [[#questions|Asking Questions And Getting Feedback]]
  
  <<Anchor(pre)>>
@@ -27, +28 @@

  '''Note:''' You're still welcome to submit patches even if an issue has been assigned to
someone else. In this case, it's probably better to add a comment before getting started.

  
  <<Anchor(step2)>>
+ == Step 2: Run the tests ==
+  * Instructions are here: http://wiki.apache.org/couchdb/How_to_create_tests?action=show

+  * Run the tests at least before you start coding and when you're done.
+ 
+ <<Anchor(step3)>>
- == Step 2: Go forth and code! ==
+ == Step 3: Go forth and code! ==
   * Take a look at the recommended coding standards here: [[Coding_Standards]]
   * Before starting, make sure that your local copy is up to the latest version
   * For those using the command-line subversion tools, run this before starting:
@@ -41, +47 @@

  $ make dev
   }}}
  
- <<Anchor(step3)>>
+ <<Anchor(step4)>>
- == Step 3: Create and Upload a Patch ==
+ == Step 4: Create and Upload a Patch ==
   * Once you've completed the feature/fix you will need to create a patch
   * From the command line, call the following, giving your patch a name:
   {{{

Mime
View raw message