Twice now I've assumed that release.py --bump would check in its
changes, and scotched the release. Changing PEP 101 to hopefully prevent this for 3.4.0a3.
This commit is contained in:
parent
3d5f0c8eb7
commit
523919a147
|
@ -192,7 +192,8 @@ How to Make A Release
|
|||
content of this file. You should only need to review the text for
|
||||
sanity, and update the release date with today's date.
|
||||
|
||||
Commit the changes once you have reviewed them.
|
||||
___ Make sure all changes have been committed. (``release.py --bump``
|
||||
doesn't check in its changes for you.)
|
||||
|
||||
___ Check the years on the copyright notice. If the last release
|
||||
was some time last year, add the current year to the copyright
|
||||
|
|
Loading…
Reference in New Issue