[wiki.rietveld] push by - how to run Rietveld on 2012-02-13 09:57 GMT

[riet...@googlecode.com]

Revision: 5bfc5e583d9e
Author: tech...@gmail.com
Date: Mon Feb 13 01:57:51 2012
Log: how to run Rietveld
http://code.google.com/p/rietveld/source/detail?r=5bfc5e583d9e&repo=wiki

Modified:
/Contributing.wiki

=======================================
--- /Contributing.wiki Fri Dec 16 01:31:38 2011
+++ /Contributing.wiki Mon Feb 13 01:57:51 2012
@@ -3,7 +3,7 @@
== tl;dr ==

{{{
-upload.py -r albrec...@googlemail.com,tech...@gmail.com
--cc=coderev...@googlegroups.com --send_mail
+python upload.py -r albrec...@googlemail.com,tech...@gmail.com
--cc=coderev...@googlegroups.com --send_mail
}}}

several small patches are better than a huge one, demo helps,
[http://code.google.com/p/rietveld/source/browse/wiki/Contributing.wiki?edit=1
improvements] are welcome.
@@ -21,11 +21,18 @@
hg clone https://code.google.com/p/rietveld/
cd rietveld
}}}
+
+=== Make it running ===
+Download
[http://code.google.com/appengine/downloads.html#Google_App_Engine_SDK_for_Python
AppEngine SDK]. Run Rietveld locally with App Engine Launcher (Windows,
MacOS) or command line on Linux:
+{{{
+# change path to AppEngine SDK
+SDK_PATH=../appengine make serve
+}}}

=== Prepare a patch ===
Split it into munchable chunks if you can. 5 simple patches will be more
likely accepted much-much faster than a big complex one. This requires some
kind of patch queue management effort on your side, but let's hope some day
we'll streamline the process.

-=== Run the test suite ===
+=== Execute test suite ===
Make sure that your patch didn't break anything and run the test suite:

{{{