Show More
@@ -29,9 +29,8 b' Some guidelines on contributing to IPython:' | |||
|
29 | 29 | - bugfixes should include regression tests |
|
30 | 30 | - new behavior should at least get minimal exercise |
|
31 | 31 | * New features and backwards-incompatible changes should be documented by adding |
|
32 |
a new file to the [ |
|
|
33 |
|
|
|
34 | details. | |
|
32 | a new file to the [pr](docs/source/whatsnew/pr) directory, see [the README.md | |
|
33 | there](docs/source/whatsnew/pr/README.md) for details. | |
|
35 | 34 | |
|
36 | 35 | [Travis](http://travis-ci.org/#!/ipython/ipython) does a pretty good job testing IPython and Pull Requests, |
|
37 | 36 | but it may make sense to manually perform tests (possibly with our `test_pr` script), |
@@ -7,8 +7,8 b' directory documenting this change as a part of your Pull Request.' | |||
|
7 | 7 | |
|
8 | 8 | This will allow multiple Pull Requests to do the same without conflicting with |
|
9 | 9 | one another. Periodically, IPython developers with commit rights will run a |
|
10 |
script and populate [develop |
|
|
11 | of this directory, and clean it up. | |
|
10 | script and populate [development.rst](../development.rst) | |
|
11 | with the contents of this directory, and clean it up. | |
|
12 | 12 | |
|
13 | 13 | Files which describe new features can have any name, such as |
|
14 | 14 | `antigravity-feature.rst`, whereas backwards incompatible changes should have a |
General Comments 0
You need to be logged in to leave comments.
Login now