DOC : added folders for api_changes and whats_new #3349
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added README + folders for whats_new and api_changes files. The idea is instead of everyone editing the same file (which leads to frequent conflicts requiring either manual merging or re-basing) each entry will create a new file which will be assembled into a single file during the release.
| in this folder with the name YYYY-MM-DD-[initials].rst (ex 2014-07-31-TAC.rst) | ||
| with contents following the form: | ||
|
|
||
| Brief destription of change |
- fixed typos - changed txt -> rst so gh will display it nicely (maybe?) - minor prose change to be clearer
This was referenced Aug 9, 2014
|
@efiring Can you merge this when you get a chance? I want to start having new PRs make use of the folder scheme |
efiring
added a commit
that referenced
this pull request
Aug 17, 2014
DOC : added folders for api_changes and whats_new
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added README + folders for whats_new and api_changes files.
The idea is instead of everyone editing the same file (which leads to
frequent conflicts requiring either manual merging or re-basing) each
entry will create a new file which will be assembled into a single file
during the release.