Commits

Matthew Turk committed dd9ccbb

Responding to Britton's suggestions

Comments (0)

Files changed (1)

source/advanced/developing.rst

 
   * New Features
 
-    * New unit tests (possibly new answer tests)
+    * New unit tests (possibly new answer tests) (See :ref:`testing`)
     * Docstrings for public API
     * Addition of new feature to the narrative documentation
     * Addition of cookbook recipe
 
     * Update existing narrative docs and docstrings
     * Update existing cookbook recipes
-    * Modify of create new unit tests
+    * Modify of create new unit tests (See :ref:`testing`)
     * Issue created on issue tracker, to ensure this is added to the changelog
 
   * Bug fixes
 walk you through any troubles you might have.  Here are some suggestions
 for using mercurial with yt:
 
-  * Named branches are probably to be avoided.  Try using bookmarks (``hg
-    bookmark``) to track work.  (`More
-    <http://mercurial.selenic.com/wiki/Bookmarks>`_)
+  * Named branches are to be avoided.  Try using bookmarks (``hg bookmark``) to
+    track work.  (`More <http://mercurial.selenic.com/wiki/Bookmarks>`_)
   * Make sure you set a username in your ``~/.hgrc`` before you commit any
     changes!  All of the tutorials above will describe how to do this as one of
     the very first steps.
   #. Commit these changes, using ``hg commit``.  This can take an argument
      which is a series of filenames, if you have some changes you do not want
      to commit.
+  #. If your changes include new functionality or cover an untested area of the
+     code, add a test.  (See :ref:`testing` for more information.)  Commit
+     these changes as well.
   #. Push your changes to your new fork using the command::
 
      hg push https://bitbucket.org/YourUsername/yt/