Show More
@@ -1,18 +1,18 b'' | |||
|
1 | 1 | Documenting What's New |
|
2 | 2 | ---------------------- |
|
3 | 3 | |
|
4 | 4 | When making a new pull request that either adds a new feature, or makes a |
|
5 | 5 | backwards-incompatible change to IPython, please add a new `.rst` file in this |
|
6 | 6 | 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 | 10 | script and populate [development.rst](../development.rst) |
|
11 | 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 |
`antigravity-feature.rst`, whereas backwards incompatible changes |
|
|
15 |
filename starting with `incompat-`, such as |
|
|
16 | Our "What's new" files always have two sections, and this prefix scheme will | |
|
17 | make sure that the backwards incompatible changes get routed to their proper | |
|
18 | section. | |
|
14 | `antigravity-feature.rst`, whereas backwards incompatible changes **must have** | |
|
15 | have a filename starting with `incompat-`, such as | |
|
16 | `incompat-switching-to-perl.rst`. Our "What's new" files always have two | |
|
17 | sections, and this prefix scheme will make sure that the backwards incompatible | |
|
18 | changes get routed to their proper section. |
General Comments 0
You need to be logged in to leave comments.
Login now