mention lintChanges.py in the coding standards

This commit is contained in:
Nick Mathewson 2016-02-01 16:47:47 -05:00
parent deea08c13f
commit 311a13220c
1 changed files with 5 additions and 0 deletions

View File

@ -80,6 +80,11 @@ When we go to make a release, we will concatenate all the entries
in changes to make a draft changelog, and clear the directory. We'll
then edit the draft changelog into a nice readable format.
To make sure that stuff is in the right format, we use
scripts/maint/lintChanges.py to check the changes files for
(superficial) validity. You can run this script on your own changes
files!
What needs a changes file?
* A not-exhaustive list: Anything that might change user-visible