[Python-checkins] python/nondist/peps pep-0102.txt,1.7,1.8
bwarsaw@users.sourceforge.net
bwarsaw@users.sourceforge.net
Thu, 22 May 2003 14:33:28 -0700
Update of /cvsroot/python/python/nondist/peps
In directory sc8-pr-cvs1:/tmp/cvs-serv4899
Modified Files:
pep-0102.txt
Log Message:
Updates based on the Python 2.2.3 release. There may be more...
Index: pep-0102.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0102.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** pep-0102.txt 12 Aug 2002 11:42:43 -0000 1.7
--- pep-0102.txt 22 May 2003 21:33:26 -0000 1.8
***************
*** 79,82 ****
--- 79,87 ----
these are necessary for a new micro, minor or major release.
+ The LICENSE fie contains a table that describes the legal
+ heritage of Python; you should add an entry for the X.Y.Z
+ release you are now making. You should update this table in the
+ LICENSE file on the CVS trunk too.
+
___ When the year changes, copyright legends need to be updated in
many places, including the README and LICENSE files.
***************
*** 148,154 ****
You should not see any "M" files, but you may see several "P"
! files. I.e. you better not have any uncommitted changes in your
! working directory, but you may pick up some of Fred's or Tim's
! last minute changes.
___ Now tag the branch using a symbolic name like "rXYMaZ",
--- 153,159 ----
You should not see any "M" files, but you may see several "P"
! and/or "U" files. I.e. you better not have any uncommitted
! changes in your working directory, but you may pick up some of
! Fred's or Tim's last minute changes.
___ Now tag the branch using a symbolic name like "rXYMaZ",
***************
*** 156,159 ****
--- 161,167 ----
% cvs tag r212
+ Be sure to tag only the python/dist/src subdirectory of the
+ Python CVS tree!
+
___ Change to a neutral directory, i.e. one in which you can do a
fresh, virgin, cvs export of the branch. You will be creating a
***************
*** 162,166 ****
% cd ~
! % cvs -d <cvsroot> export -rr212 -d Python-2.1.2 python/dist/src
___ Generate the tarball. Note that we're not using the `z' option
--- 170,174 ----
% cd ~
! % cvs -d cvs.sf.net:/cvsroot/python export -rr212 -d Python-2.1.2 python/dist/src
___ Generate the tarball. Note that we're not using the `z' option
***************
*** 205,246 ****
include the announcement.
! ___ In the python.org web site CVS tree, cd to the X.Y
! subdirectory, and copy index.ht to new-index.ht. Be sure to
! do a "cvs update" first!
% cd .../pydotorg
! % cvs -q up -P -d
! % cd 2.2
! % cp index.ht new-index.ht
! ___ Edit the file for content: usually you can globally replace
X.Ya(Z-1) with X.YaZ. However, you'll need to think about the
"What's New?" section.
! ___ Copy the Misc/NEWS file to NEWS.txt in the X.Y directory for
python.org; this contains the "full scoop" of changes to
Python since the previous release for this version of Python.
- If this is the first release in a series (e.g. 2.2.1c1) then
- you'll need to create a new directory (e.g. 2.2.1). It's
- probably best to copy the last directory across:
-
- % cp -r 2.2 2.2.1
- % rm -rf 2.2.1/CVS
- % cvs add 2.2.1
-
- and then make changes as needed. Verbiage from prereleases of
- previous versions can be found in CVS if you're feeling uninspired.
-
___ Also, update the MD5 checksums.
! ___ Preview the web page by doing a "make" -- NOT a "make install".
! View the page via a file: url.
___ Similarly, edit the ../index.ht file, i.e. the python.org home
page. In the Big Blue Announcement Block, move the paragraph
for the new version up to the top and boldify the phrase
! "Python X.YaZ is out". Edit for content, and preview as
! above. Do NOT do a "make install" yet!
___ Now we're waiting for the scp to creosote to finish. Da de da,
--- 213,245 ----
include the announcement.
! ___ In the top of the python.org web site CVS tree, create a
! subdirectory for the X.Y.Z release. You can actually copy an
! earlier patch release's subdirectory, but be sure to delete
! the X.Y.Z/CVS directory and "cvs add X.Y.Z", for example:
% cd .../pydotorg
! % cp -r 2.2.2 2.2.3
! % rm -rf 2.2.3/CVS
! % cvs add 2.2.3
! % cd 2.2.3
! ___ Edit the files for content: usually you can globally replace
X.Ya(Z-1) with X.YaZ. However, you'll need to think about the
"What's New?" section.
! ___ Copy the Misc/NEWS file to NEWS.txt in the X.Y.Z directory for
python.org; this contains the "full scoop" of changes to
Python since the previous release for this version of Python.
___ Also, update the MD5 checksums.
! ___ Preview the web page by doing a "make" or "make install" (as
! long as you've created a new directory for this release!)
___ Similarly, edit the ../index.ht file, i.e. the python.org home
page. In the Big Blue Announcement Block, move the paragraph
for the new version up to the top and boldify the phrase
! "Python X.YaZ is out". Edit for content, and preview locally,
! but do NOT do a "make install" yet!
___ Now we're waiting for the scp to creosote to finish. Da de da,
***************
*** 277,288 ****
BDFL input for this step.
! ___ Now preview the new-index.ht file once more. IMPORTANT: follow
! every link on the page to make sure it goes where you expect it
! to go, and that what you expect to be there is there.
!
! ___ If everything looks good, move new-index.ht to index.ht and do a
! "make install" in this directory. Go up to the parent directory
! (i.e. the root of the web page hierarchy) and do a "make
! install" there too. You're release is now live!
___ Now it's time to write the announcement for the mailing lists.
--- 276,282 ----
BDFL input for this step.
! ___ Go up to the parent directory (i.e. the root of the web page
! hierarchy) and do a "make install" there. You're release is now
! live!
___ Now it's time to write the announcement for the mailing lists.