# HG changeset patch # User Marcin Kuzminski # Date 1330718827 -7200 # Node ID 6fdc3b25bc7c9360aaaa23d2784ce423e286e4bb # Parent 7172d88f3cee292b36482f43903aae8ad3b55a4c docs diff -r 7172d88f3cee -r 6fdc3b25bc7c docs/contributing.rst --- a/docs/contributing.rst Fri Mar 02 22:02:44 2012 +0200 +++ b/docs/contributing.rst Fri Mar 02 22:07:07 2012 +0200 @@ -14,16 +14,19 @@ stable, and not the other way. Finally, when you are finished making a change, please send me a pull request. -To run RhodeCode in a development version you always need to install the tip -version of RhodeCode and the VCS library. +To run RhodeCode in a development version you always need to install the latest +required libs from `requires.txt` file. -after downloading RhodeCode make sure you run:: +after downloading/pulling RhodeCode make sure you run:: python setup.py develop -command to install all required packages, and prepare development enviroment +command to install/verify all required packages, and prepare development +enviroment. +After finishing your changes make sure all tests passes ok. You can run +the testsuite running nosetest from the project root. | Thank you for any contributions! | Marcin diff -r 7172d88f3cee -r 6fdc3b25bc7c docs/upgrade.rst --- a/docs/upgrade.rst Fri Mar 02 22:02:44 2012 +0200 +++ b/docs/upgrade.rst Fri Mar 02 22:07:07 2012 +0200 @@ -25,11 +25,11 @@ This will display any changes made by the new version of RhodeCode to your current configuration. It will try to perform an automerge. It's always better -to make a backup of your configuration file before hand and recheck the +to make a backup of your configuration file before hand and re check the content after the automerge. .. note:: - Please always make sure your .ini files are upto date. Often errors are + Please always make sure your .ini files are up to date. Often errors are caused by missing params added in new versions.