summaryrefslogtreecommitdiffstats
path: root/HOWTO
diff options
context:
space:
mode:
authorSteven Knight <knight@baldmt.com>2002-01-11 08:46:19 (GMT)
committerSteven Knight <knight@baldmt.com>2002-01-11 08:46:19 (GMT)
commitdd40d81aa957e6c4724c648bf74390280849e944 (patch)
tree3ccf8d7dae4aef9daa56a9f64e2d5f57de1cff62 /HOWTO
parent9deba5890b7df92692c3492c612231182efb3e90 (diff)
downloadSCons-dd40d81aa957e6c4724c648bf74390280849e944.zip
SCons-dd40d81aa957e6c4724c648bf74390280849e944.tar.gz
SCons-dd40d81aa957e6c4724c648bf74390280849e944.tar.bz2
Initialize the new branch.
Diffstat (limited to 'HOWTO')
-rw-r--r--HOWTO/change.txt20
-rw-r--r--HOWTO/release.txt72
2 files changed, 61 insertions, 31 deletions
diff --git a/HOWTO/change.txt b/HOWTO/change.txt
index f12f9a1..b83c01a 100644
--- a/HOWTO/change.txt
+++ b/HOWTO/change.txt
@@ -30,28 +30,28 @@ Handling a change set:
-- Distribute the change to scons-aedist:
- aedist -s -p scons.0.3 {cnum} > scons.0.3.C{cnum}.ae
- pine -attach scons.0.3.C{cnum}.ae scons-aedist@lists.sourceforge.net
- Subject: scons.0.3 - {SUMMARY}
- Body: aegis -l -p scons.0.3 -c {cnum} cd
+ aedist -s -p scons.0.4 {cnum} > scons.0.4.C{cnum}.ae
+ pine -attach scons.0.4.C{cnum}.ae scons-aedist@lists.sourceforge.net
+ Subject: scons.0.4 - {SUMMARY}
+ Body: aegis -l -p scons.0.4 -c {cnum} cd
- rm scons.0.3.C{cnum}.ae
+ rm scons.0.4.C{cnum}.ae
[This will eventually be automated.]
-- Update the aedist baseline on the web site:
- aedist -s -bl -p scons.0.3 > scons.0.3.ae
- scp scons.0.3.ae stevenknight@scons.sourceforge.net:/home/groups/s/sc/scons/htdocs/scons.0.3.ae
- rm scons.0.3.ae
+ aedist -s -bl -p scons.0.4 > scons.0.4.ae
+ scp scons.0.4.ae stevenknight@scons.sourceforge.net:/home/groups/s/sc/scons/htdocs/scons.0.4.ae
+ rm scons.0.4.ae
[This will eventually be automated.]
-- Distribute the change to CVS:
export CVS_RSH=ssh
- ae2cvs -n -aegis -p scons.0.3 -c {cnum} -u ~/SCons/scons
- ae2cvs -X -aegis -p scons.0.3 -c {cnum} -u ~/SCons/scons
+ ae2cvs -n -aegis -p scons.0.4 -c {cnum} -u ~/SCons/scons
+ ae2cvs -X -aegis -p scons.0.4 -c {cnum} -u ~/SCons/scons
If you need the "ae2cvs" Perl script, you can find a copy
checked in to the bin/subdirectory.
diff --git a/HOWTO/release.txt b/HOWTO/release.txt
index 9cbd498..6a210ba 100644
--- a/HOWTO/release.txt
+++ b/HOWTO/release.txt
@@ -46,11 +46,11 @@ Things to do to release a version of SCons:
ae_p scons.0
- aede scons {2}
+ aede {4}
- aerpass {2}
+ aerpass {4}
- aeib {2}
+ aeib {4}
aeb
@@ -64,15 +64,15 @@ Things to do to release a version of SCons:
START THE NEW BRANCH
- aenbr -p scons.0 {3}
+ aenbr -p scons.0 {5}
- aenc -p {scons.0.3}
+ aenc -p {scons.0.5}
Call it something like, "Initialize the new
branch." Cause = internal_enhancement. Exempt
it from all tests (*_exempt = true).
- ae_p scons.0.3
+ ae_p scons.0.5
aedb 100
@@ -112,15 +112,23 @@ Things to do to release a version of SCons:
<your email>
cd incoming
bin
- put scons-0.02-1.noarch.rpm
- put scons-0.02-1.src.rpm
- put scons-0.02.tar.gz
- put scons-0.01.win32.exe
- put scons-src-0.01.tar.gz
- put scons_0.01-1_all.deb
+ put scons-0.04-1.noarch.rpm
+ put scons-0.04-1.src.rpm
+ put scons-0.04.tar.gz
+ put scons-0.04.win32.exe
+ put scons-src-0.04.tar.gz
+ put scons_0.04-1_all.deb
Create the new release at the SourceForge project page:
+ Go to the Admin page
+
+ => Edit/Add File Releases
+
+ => Add Release
+
+ New release name: 0.04
+
Cut-and-paste or upload the RELEASE.txt file.
Cut-and-paste or upload the CHANGES.txt file.
@@ -132,14 +140,14 @@ Things to do to release a version of SCons:
Click "Submit/Refresh"
- Edit the files
+ Edit the file info:
- scons-0.02-1.noarch.rpm Any .rpm
- scons-0.02-1.src.rpm Any Source .rpm
- scons-0.02.tar.gz Any .gz
- scons-0.01.win32.exe i386 Other
- scons-src-0.01.tar.gz Any Source .gz
- scons_0.01-1_all.deb Any .deb
+ scons-0.04-1.noarch.rpm Any .rpm
+ scons-0.04-1.src.rpm Any Source .rpm
+ scons-0.04.tar.gz Any .gz
+ scons-0.04.win32.exe i386 Other
+ scons-src-0.04.tar.gz Any Source .gz
+ scons_0.04-1_all.deb Any .deb
(This has to be done one at a time.)
@@ -168,20 +176,38 @@ Things to do to release a version of SCons:
+ In the Bugs Tracker, add a Group for the new release (0.04)
+
+
+
Announce to the following mailing lists (template below):
scons-announce@lists.sourceforge.net
scons-users@lists.sourceforge.net
scons-devel@lists.sourceforge.net
- python-list@python.org
+ [right away]
python-announce@python.org
- [optional] cons-discuss@gnu.org
+ [right away, it's moderated and will take
+ some time to get through]
linux-announce@news.ornl.gov
+ [right away, it's moderated and will take
+ some time to get through]
+
+ [optional] cons-discuss@gnu.org
+
+ [only if it's a really big announcement,
+ I said we wouldn't bug this list]
+
+ python-list@python.org
+
+ [wait until business hours so the announcemnt
+ hits mailboxes while U.S. workers are active]
+
Notify www.cmtoday.com/contribute.html
[This guy wants an announcement no more frequently than
@@ -190,6 +216,10 @@ Things to do to release a version of SCons:
Notify freshmeat.net
+ [Wait until the morning so the announcement hits the
+ main freshmeat.net page while people in the U.S. are
+ awake and working]
+