Add a bit more to the developer's documentation

I'm not sure what else could be added to satisfy #601. If this is sufficient,
I suggest closing that.

diff --git a/docs/dev/todo.rst b/docs/dev/todo.rst
index 7aa2cae8f5bc00bf43f1ebf3fe8718136d5314f3..e9930a8eae8f6dd6cb96784a71d6690218918c22 100644 (file)
--- a/docs/dev/todo.rst
+++ b/docs/dev/todo.rst
@@ -23,7 +23,19 @@ order to run requests' test suite::
     $ make
     $ make test
 
-The ``Makefile`` has various useful targets for testing.
+The ``Makefile`` has various useful targets for testing. For example, if you 
+want to see how your pull request will behave with Travis-CI you would run 
+``make travis``.
+
+Versions of Python to Test On
+-----------------------------
+
+Officially (as of 26-Nov-2012), requests supports python 2.6-3.3. In the 
+future, support for 3.1 and 3.2 may be dropped. In general you will need to 
+test on at least one python 2 and one python 3 version. You can also set up 
+Travis CI for your own fork before you submit a pull request so that you are 
+assured your fork works. To use Travis CI for your fork and other projects see 
+their `documentation <http://about.travis-ci.org/docs/user/getting-started/>`_.
 
 What Needs to be Done
 ---------------------