From 898d79e4122ce7d06b89d06b4fafa08d7befa501 Mon Sep 17 00:00:00 2001 From: "Kurt B. Kaiser" Date: Fri, 5 Dec 2003 00:45:14 +0000 Subject: [PATCH] Add IDLE tasks. Modified Files: pep-0101.txt pep-0102.txt --- pep-0101.txt | 9 +++++++++ pep-0102.txt | 4 ++++ 2 files changed, 13 insertions(+) diff --git a/pep-0101.txt b/pep-0101.txt index 91eff9816..e2ef0f375 100644 --- a/pep-0101.txt +++ b/pep-0101.txt @@ -95,6 +95,9 @@ How to Make A Release ___ For major releases (e.g. 2.3 final), move any historical "what's new" entries from Misc/NEWS to Misc/HISTORY. + ___ Check with the IDLE maintainer to be sure that + Lib/idlelib/NEWS.txt has been similarly updated. + ___ Tag and/or branch the tree for release X.YaZ If you're releasing an alpha/beta/release candidate, you will @@ -139,6 +142,12 @@ How to Make A Release to change the PY_VERSION macro, and one or several of the version subpart macros just above PY_VERSION, as appropriate. + ___ IDLE maintains its own versioning and NEWS file (Lib/idlelib/NEWS.txt). + There should be a number of entries reflecting new development, under a + temporary header. Update that header to reflect IDLE's new version and + release date. Then update Lib/idlelib/idlever.py to show a matching + version. + ___ Change the "%define version" line of Misc/RPM/python-2.3.spec to the same string as PY_VERSION was changed to above. E.g. diff --git a/pep-0102.txt b/pep-0102.txt index b0ee7057f..e589aaf90 100644 --- a/pep-0102.txt +++ b/pep-0102.txt @@ -137,6 +137,10 @@ How to Make A Release ___ Check your NEWS changes into the maintenance branch. It's easy to forget to update the release date in this file! + ___ Check in any changes to IDLE's NEWS.txt. Update the header in + Lib/idlelib/NEWS.txt to reflect its release version and date. + Update the IDLE version in Lib/idlelib/idlever.py to match. + ___ Once the release process has started, the documentation needs to be built and posted on python.org according to the instructions in PEP 101.