1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
|
Things to do to release a version of SCons:
Build and test candidate packages
test on Linux
test on Windows NT
1) tar zxf scons-src-{version}.tar.gz
cd scons-src-{version}
python runtest.py -a
2) tar zxf scons-{version}.tar.gz
cd scons-{version}
python setup.py install
cd scons-src-{version}
python runtest.py -a -x C:\Python15\scons.bat
3) scons-{verson}.win32.exe
cd scons-src-{version}
python runtest.py -a -x C:\Python15\scons.bat
Read through the README.txt file for any updates
Prepare src/CHANGES.txt
date -R the latest release
should be current if this has been updated as each
change went in.
Prepare src/RELEASE.txt
date -R the latest release
Can probably keep a lot of the existing text, read
it through to make sure it's okay and edit appropriately.
Prepare debian/changelog
date -R the latest release
END THE BRANCH
ae_p scons.0
aede scons {2}
aerpass {2}
aeib {2}
aeb
aet
aet -reg
aed
aeipass
START THE NEW BRANCH
aenbr -p scons.0 {3}
aenc -p {scons.0.3}
Call it something like, "Initialize the new
branch." Cause = internal_enhancement. Exempt
it from all tests (*_exempt = true).
ae_p scons.0.3
aedb 100
aecd
# Change the hard-coded package version numbers
# in the following files.
aecp Construct debian/changelog rpm/scons.spec
vi Construct debian/changelog rpm/scons.spec
# Optionally, do the same in the following:
[optional] aecp HOWTO/change.txt debian/scons.postinst
[optional] vi HOWTO/change.txt debian/scons.postinst
aeb
aet -reg
aed
aede
etc.
Read through the FAQ for any updates
Upload the packages to the SourceForge incoming FTP:
ftp upload.sourceforge.net
anonymous
<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
Create the new release at the SourceForge project page:
Cut-and-paste or upload the RELEASE.txt file.
Cut-and-paste or upload the CHANGES.txt file.
(If you cut-and-paste, check the "Preserve my
pre-formatted text." box!)
Check the SCons files you uploaded
Click "Submit/Refresh"
Edit the files
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
(This has to be done one at a time.)
Test downloading from the SourceForge project page
You'll need to wait a good bit; they update this on, at
best, half-hour cycles.
Update the web site:
template: new version number
src/index.in: announcement on the home page
src/scons-doc.tar.gz: update
src/CHANGES.txt: update
Test downloading from the web site download page
Add news item to the SourceForge project page
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
python-announce@python.org
[optional] cons-discuss@gnu.org
linux-announce@news.ornl.gov
Notify www.cmtoday.com/contribute.html
[This guy wants an announcement no more frequently than
once a month, so save it for a future release if it's
been too soon since the previous one.]
Notify freshmeat.net
=======================
Template release announcement:
I'm pleased to announce that version 0.XXX of SCons has been released
and is available for download from the SCons web site:
http://www.scons.org/
Or through the download link at the SCons project page at SourceForge:
http://sourceforge.net/projects/scons/
RPM and Debian packages and a Win32 installer are all available, in
addition to the traditional .tar.gz files.
SCons is a software construction tool (build tool, make tool) written
in Python. Its design is based on the design which won the Software
Carpentry build tool competition in August 2000 (in turn derived from
the Perl-based Cons build tool).
Distinctive features of SCons include:
- configuration files are Python scripts, allowing the full use of a
real scripting language to solve build problems
- a modular architecture allows the SCons Build Engine to be
embedded in other Python software
- a global view of all dependencies; no multiple passes to get
everything built
- the ability to scan files for implicit dependencies (#include files);
- improved parallel build (-j) support
- use of MD5 signatures to decide if a file has changed
- easily extensible through user-defined Builder and Scanner objects
An scons-users mailing list has been created for those interested in
getting started using SCons. You can subscribe at:
http://lists.sourceforge.net/lists/listinfo/scons-users
Alternatively, we invite you to subscribe to the low-volume
scons-announce mailing list to receive notification when new versions of
SCons become available:
http://lists.sourceforge.net/lists/listinfo/scons-announce
Special thanks to XXX for his/her/their contributions to this release.
On behalf of the SCons team,
--SK
|
