Add a note about the necessity of updating the LICENSE file.
This commit is contained in:
parent
7e08ee9b55
commit
bcedb64c4b
11
pep-0102.txt
11
pep-0102.txt
|
@ -71,8 +71,15 @@ How to Make A Release
|
|||
Python 2.1.1 to Python 2.1.2), you also need to update the
|
||||
README file, which has a big banner at the top proclaiming its
|
||||
identity. Don't do this if you're just releasing a new alpha or
|
||||
beta release, but /do/ do this if you're release a new micro
|
||||
release.
|
||||
beta release, but /do/ do this if you're release a new micro,
|
||||
minor or major release.
|
||||
|
||||
___ The LICENSE file also needs to be changed, due to several
|
||||
references to the release number. As for the README file, changing
|
||||
these are necessary for a new micro, minor or major release.
|
||||
|
||||
___ When the year changes, copyright legends need to be updated in
|
||||
many places, including the README and LICENSE files.
|
||||
|
||||
___ After starting the process, the most important thing to do next
|
||||
is to update the Misc/NEWS file. Tim will need this in order to
|
||||
|
|
Loading…
Reference in New Issue