Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Newer
Older
100644 302 lines (211 sloc) 9.641 kb
f45384ae »
2009-02-26 First version of release_guide.pod, based on a proposed version
1 =head1 release_guide.pod - guide to Rakudo releases
2
3 Rakudo's development release cycle is based on Parrot's release
4 cycle. Parrot releases the third Tuesday of each month; Rakudo
5 will generally issue its own development release two days after
6 the Parrot release.
7
8 Each development release is given a sequential number and a
9 code name based on an active Perl Mongers group. Rakudo's
10 February 2009 release is #14; prior releases were bundled as
11 part of monthly Parrot releases.
12
13 =head2 Development releases
14
5b477c08 »
2009-07-28 Note the release manager for each of the previous releases,
15 2009-02-26 Rakudo #14 "Vienna" (pmichaud)
16 2009-03-20 Rakudo #15 "Oslo" (pmichaud)
17 2009-04-23 Rakudo #16 "Bratislava" (pmichaud)
18 2009-05-21 Rakudo #17 "Stockholm" (pmichaud)
19 2009-06-18 Rakudo #18 "Pittsburgh" (pmichaud)
20 2009-07-23 Rakudo #19 "Chicago" (moritz)
cf27952f »
2009-08-19 [docs] bare bones 2009-08 announcement and release_guide update
21 2009-08-20 Rakudo #20 "PDX" (kyle)
e33d20ee »
2009-09-26 [docs] mention smolder reports in release_guide.pod
22 2009-09-17 Rakudo #21 "Seattle" (particle)
37956bfc »
2009-10-22 Updates in preparation for release
23 2009-10-22 Rakudo #22 "Thousand Oaks" (duff)
f5065b6e »
2009-11-19 [docs/release_guide.pod] rolled releases forward
24 2009-11-19 Rakudo #23 "Lisbon" (masak)
7f1c3fe8 »
2009-12-17 [docs] Updated release guide.
25 2009-12-17 Rakudo #24 "Seoul" (chromatic)
4da4e4d7 »
2010-01-22 Update release dates and names.
26 2010-01-22 Rakudo #25 "Minneapolis" (pmichaud)
37e57468 »
2010-03-04 Update release_guide.pod with recent release information.
27 2010-02-18 Rakudo #26 "Amsterdam" (mberends)
fc30fad4 »
2010-04-02 [docs] the Copenhagen release has already happend; colomon++ voluntue…
28 2010-03-18 Rakudo #27 "Copenhagen" (smash)
05ee8243 »
2010-04-22 [docs] update release guide
29 2010-04-22 Rakudo #28 "Moscow" (moritz)
296a56c7 »
2010-05-20 Add #29 Erlangen to the release list, and mark that [Coke] has the Ju…
30 2010-05-20 Rakudo #29 "Erlangen" (colomon)
cbff7d0c »
2010-06-18 [docs/release_guide.pod] updates and improvements
31 2010-06-17 Rakudo #30 "Kiev" (masak)
5c33c5aa »
2010-07-22 This release is heading out the door soon.
32 2010-07-22 Rakudo #31 "Atlanta" (Coke)
99a4e24d »
2010-08-19 Update release guide with 2010.08 release.
33 2010-08-19 Rakudo #32 "Pisa" (mathw)
74a156f3 »
2010-09-23 [release] name is Milan. Bump VERSION
34 2010-09-23 Rakudo #33 "Milan" (moritz)
33bdceee »
2010-10-21 release preparation
35 2010-10-21 Rakudo #34 "Paris" (duff)
03e6f5a2 »
2010-11-18 [docs/release_guide.pod] slight tweaks
36 2010-11-18 Rakudo #35 "Melbourne" (masak)
4830af68 »
2010-12-23 [release] update release guide
37 2010-12-23 Rakudo #36 "New York" (smash)
a7d5f19f »
2011-01-20 Added announcement for 2011.01
38 2011-01-20 Rakudo #37 "BristolBath" (tadzik)
c25afe6a »
2011-02-17 [release] Add announcement, updated release guide. Added own name and
39 2011-02-17 Rakudo #38 "Toulouse" (arnsholt)
e70f27d6 »
2011-03-17 [release] Add announcement, update release gude and add myself to
40 2011-03-17 Rakudo #39 "Orlando" (jdhore)
16244913 »
2011-09-27 copy release_guide.pod changes from master, renumber for missed 2011.…
41 2011-04-21 Rakudo #40 "ZA" (duff)
42 2011-05-19 Rakudo #41 "Dahut" (jdhore)
43 2011-06-23 Rakudo #42 "Bruxelles" (jdhore)
44 2011-07-21 Rakudo #43 "Beijing" (mberends,moritz)
45 2011-08-18 -- none --
01d3a6b7 »
2011-09-28 Update release info
46 2011-09-30 Rakudo #44 "Riga" (tadzik)
e17c139a »
2011-10-20 Choose a release name
47 2011-10-20 Rakudo #45 "Houston" (duff)
617fef96 »
2011-11-17 Add a new release announcement, update release_guide
48 2011-11-17 Rakudo #46 "London" (tadzik)
dfd1d7ac »
2011-12-22 update release guide
49 2011-12-22 Rakudo #47 "Columbus" (moritz)
63663bd3 »
2012-01-23 correct release date and copyright in release_guide.pod
50 2012-01-23 Rakudo #48 "Toronto" (moritz)
a95379da »
2012-02-23 [docs/release_guide.pod] updated
51 2012-02-23 Rakudo #49 "SPb" (masak)
5dda9a71 »
2012-03-22 [docs/release_guide.doc] current release => past
52 2012-03-22 Rakudo #50 "Argentina" (masak)
65ab8e3d »
2012-04-19 nearly done planning...
53 2012-04-19 Rakudo #51 "Brazos Valley" (Coke)
5a65af3c »
2012-04-25 add 2012.04 release to release_guide.pod
54 2012-04-25 2012.04.1 (moritz)
8004748a »
2012-05-17 Update release guide
55 2012-05-17 Rakudo #52 "MadMongers" (tadzik)
29607d8d »
2012-06-21 update release announcement
56 2012-06-21 Rakudo #53 "Strasbourg" (duff)
9fb677fe »
2012-07-19 [docs/release_guide.pod] named current release
57 2012-07-19 Rakudo #54 "Tallinn" (masak)
f45384ae »
2009-02-26 First version of release_guide.pod, based on a proposed version
58
dfd1d7ac »
2011-12-22 update release guide
59 =head2 Planned 2012 releases
f45384ae »
2009-02-26 First version of release_guide.pod, based on a proposed version
60
61 Dates are based on Parrot's expected release schedule.
62
8004748a »
2012-05-17 Update release guide
63 2012-08-23 Rakudo #55 tadzik
5dda9a71 »
2012-03-22 [docs/release_guide.doc] current release => past
64 2012-09-20 Rakudo #56
6bee9b61 »
2012-04-25 [docs/release_guide.pod] claim birthday month release too
65 2012-10-18 Rakudo #57 duff
5dda9a71 »
2012-03-22 [docs/release_guide.doc] current release => past
66 2012-11-22 Rakudo #58
67 2012-12-20 Rakudo #59
f45384ae »
2009-02-26 First version of release_guide.pod, based on a proposed version
68
381d26ea »
2009-04-22 Updates to docs/announce and docs/release_guide.pod .
69 =head2 Suggested .pm group names for future releases
70
1d49284d »
2010-01-20 [docs] Add tentative release dates through the end of 2010
71 More names can be gotten from L<http://www.pm.org> if you
72 can't think of one with any particular significance to Perl
03e6f5a2 »
2010-11-18 [docs/release_guide.pod] slight tweaks
73 6 or Rakudo.
1d49284d »
2010-01-20 [docs] Add tentative release dates through the end of 2010
74
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
75 =head2 Steps to create a release (for release managers)
76
77 Each Rakudo development release is timed to occur two
01ae3fae »
2009-09-07 [docs] propose ThousandOaks as a release name, in recognition of thei…
78 days after a Parrot monthly release.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
79
80 =over 4
81
82 =item 1.
83
03e6f5a2 »
2010-11-18 [docs/release_guide.pod] slight tweaks
84 A few days before the Parrot release, it's a good idea to...
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
85
86 =over 4
87
88 =item *
89
90 Remind people of the upcoming release, invite people to
01ae3fae »
2009-09-07 [docs] propose ThousandOaks as a release name, in recognition of thei…
91 update the ChangeLog file, update the ROADMAP, choose a
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
92 release name, etc.
93
94 =item *
95
d90f6715 »
2012-06-24 [release_guide] remove SVNisms
96 Verify that the Parrot master branch is able to build Rakudo
e33d20ee »
2009-09-26 [docs] mention smolder reports in release_guide.pod
97 and run the spectest suite. Also check the smolder reports
0d3c66ef »
2010-09-23 [docs] update release guide
98 at L<http://smolder.parrot.org/app/projects/smoke_reports/5>.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
99
100 =item *
101
d90f6715 »
2012-06-24 [release_guide] remove SVNisms
102 If Parrot's master branch exhibits any problems building or running
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
103 Rakudo (that require changes to Parrot to fix), immediately
104 report them to the Parrot development team so they can be
105 fixed prior to Parrot's release.
106
107 =item *
108
109 Review the RT queue for tickets that might need resolving
cf27952f »
2009-08-19 [docs] bare bones 2009-08 announcement and release_guide update
110 prior to the release, addressing them as needed. "Tickets
111 that need resolving" is left your discretion. Any problem
112 that has a large impact on users is worth addressing either
113 as a fix or as prominent documentation (the README and/or
114 the release announcement).
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
115
115ab2fb »
2012-06-24 Move "create release announcement" into step 1.
116 =item *
117
118 Create a draft release announcement in docs/announce/YYYY.MM .
119 You can often use the previous release's file as a starting point,
120 updating the release number, version information, name, etc. as
121 appropriate.
122
123 $ git add docs/announce/YYYY.MM
124 $ git commit docs
125
5ae28cc8 »
2012-06-30 [release-guide.pod]: Add note to update README copyright date.
126 =item *
127
128 If it's a month relatively early in the calendar year,
129 double-check that the copyright date in the README file includes
130 the current year. (It's not necessary to update copyright dates
131 in other files, unless you know that a given file has been modified
132 in a year not reflected by the file's copyright notice.)
133
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
134 =back
135
136 =item 2.
137
01ae3fae »
2009-09-07 [docs] propose ThousandOaks as a release name, in recognition of thei…
138 The short period following the Parrot release until the
139 Rakudo release is generally intended for fixing bugs,
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
140 updating documentation, and so on.
141
4b2c1fe2 »
2012-06-24 [release_guide] remove redundancy with nqp's release guide
142 =item 3.
f3eb64fc »
2011-01-16 [release_guide] Added instructions for updating the leap-second tables.
143
144 Update Rakudo's leap-second tables:
145
146 $ perl tools/update-tai-utc.pl src/core/tai-utc.pm
147
148 If a new leap second has been announced, F<tai-utc.pm> will be modified, so
149 commit the new version:
150
151 $ git commit src/core/tai-utc.pm
152
153 But probably there won't be any new leap seconds, in which case the file
154 will be unchanged.
155
96ab007e »
2012-04-19 Add note about script requirement
156 B<Note>: this program requires the perl module L<Time::y2038> be installed.
157
4b2c1fe2 »
2012-06-24 [release_guide] remove redundancy with nqp's release guide
158 =item 4.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
159
160 As the actual release date nears, review the git log history
161 to see if any additional items need to be added to the ChangeLog.
162 This can be conveniently done with "git log --since=yyyy-mm-dd --reverse".
163
48c17910 »
2009-07-07 More release_guide.pod improvements.
164 $ git commit docs/ChangeLog
165
4b2c1fe2 »
2012-06-24 [release_guide] remove redundancy with nqp's release guide
166 =item 5.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
167
115ab2fb »
2012-06-24 Move "create release announcement" into step 1.
168 When it's time to cut the release, finalize the new release
169 announcement in docs/announce/YYYY.MM. (If one hasn't already
170 been created, see step 1 above.) Highlight areas in which the
171 new release is significant. If possible, also give some small
172 details about the choice of release name. (If the details
173 are a bit lengthy, this can often best be done as a separate
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
174 section at the bottom of the announcement.)
175
082caee1 »
2010-04-27 [docs] instruct release manager to include a list of contributors in …
176 Include a list of contributors since the last release in the announcement.
177 You can get an automatically generated list by running
178
cbff7d0c »
2010-06-18 [docs/release_guide.pod] updates and improvements
179 $ perl tools/contributors.pl
082caee1 »
2010-04-27 [docs] instruct release manager to include a list of contributors in …
180
ecc4efa9 »
2011-04-21 minor modifications
181 B<Note>: this program requires the perl module L<Date::Simple> be installed.
182
082caee1 »
2010-04-27 [docs] instruct release manager to include a list of contributors in …
183 Please check the result manually for duplicates and other errors.
184
9be7890b »
2010-02-17 Update release guide to note that we now use dots instead of hyphens
185 $ git add docs/announce/YYYY.MM
48c17910 »
2009-07-07 More release_guide.pod improvements.
186 $ git commit docs
187
4eeffcaa »
2012-07-19 [docs/release_guide.pod] collapsed item numbering
188 =item 6.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
189
190 Update the release dates and names at the top of this file
4c248e5c »
2009-10-21 [docs/release_guide.pod] s/-/_/ in file name
191 (F<docs/release_guide.pod>). Also improve these instructions if
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
192 you find any steps that are missing.
193
4c248e5c »
2009-10-21 [docs/release_guide.pod] s/-/_/ in file name
194 $ git commit docs/release_guide.pod
48c17910 »
2009-07-07 More release_guide.pod improvements.
195
4eeffcaa »
2012-07-19 [docs/release_guide.pod] collapsed item numbering
196 =item 7.
5921c70d »
2012-06-24 Move the "make sure everything compiles/runs" testing step to _after_…
197
198 Create an NQP release with the same C<YYYY.MM> version number
199 as Rakudo. Follow NQP's C<docs/release_guide.pod> file to do that.
200
4eeffcaa »
2012-07-19 [docs/release_guide.pod] collapsed item numbering
201 =item 8.
5921c70d »
2012-06-24 Move the "make sure everything compiles/runs" testing step to _after_…
202
203 Go back to the Rakudo repository, and update the NQP dependency:
204
205 $ echo YYYY.MM > tools/build/NQP_REVISION
206 $ git commit -m '[release] bump NQP revision' tools/build/NQP_REVISION
207
4eeffcaa »
2012-07-19 [docs/release_guide.pod] collapsed item numbering
208 =item 9.
5921c70d »
2012-06-24 Move the "make sure everything compiles/runs" testing step to _after_…
209
210 Enter the new version into the F<VERSION> file, and commit the changes:
211
212 $ echo YYYY.MM > VERSION
213 $ git commit -m '[release] bump VERSION' VERSION
214
4eeffcaa »
2012-07-19 [docs/release_guide.pod] collapsed item numbering
215 =item 10.
5921c70d »
2012-06-24 Move the "make sure everything compiles/runs" testing step to _after_…
216
217 Make sure any locally modified files have been pushed back to github.
218
219 $ git status
220 $ git push
221
4eeffcaa »
2012-07-19 [docs/release_guide.pod] collapsed item numbering
222 =item 11.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
223
224 Make sure everything compiles and runs from a known clean state:
225
226 $ make realclean
227 $ perl Configure.pl --gen-parrot
228 $ make
229 $ make test
a63c7e05 »
2010-06-12 add stresstest target, and move day 17 of the advent tests to stresstest
230 $ make stresstest
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
231
674c9842 »
2011-04-21 [release] update release_guide
232 There are many tests to run for the stresstest target. If
233 you have a machine with multiple CPU cores, you may want to
234 execute that last as
235
236 $ TEST_JOBS=4 make stresstest
237
238 where 4 is the number of CPU cores. This should make the
239 total time to execute all of the tests dramatically less.
240
241 Continue adjusting things until make stresstest passes as expected.
3c7289b4 »
2010-01-22 Small improvement to guidelines for failing spectests at time of rele…
242 Often this means fixing a bug, fudging a test, or (temporarily?)
0d3c66ef »
2010-09-23 [docs] update release guide
243 commenting out a test file in t/spectest.data . Use your best
3c7289b4 »
2010-01-22 Small improvement to guidelines for failing spectests at time of rele…
244 judgment or ask others if uncertain what to do here.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
245
4eeffcaa »
2012-07-19 [docs/release_guide.pod] collapsed item numbering
246 =item 12.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
247
cbff7d0c »
2010-06-18 [docs/release_guide.pod] updates and improvements
248 Create a tarball by entering C<make release VERSION=YYYY.MM>,
240e2f09 »
2010-03-18 Testing commit.
249 where YYYY.MM is the month for which the release is being made.
f83304dd »
2011-09-27 [docs] markup fix
250 This will create a tarball file named C<rakudo-YYYY.MM.tar.gz>.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
251
ecc4efa9 »
2011-04-21 minor modifications
252 B<Caution>: this step removes any untracked files in F<t/spec>.
0d3c66ef »
2010-09-23 [docs] update release guide
253 So please make a backup if you have any important data in there.
e3fe329c »
2010-05-20 [docs] warn about potential damage from "make release"
254
4eeffcaa »
2012-07-19 [docs/release_guide.pod] collapsed item numbering
255 =item 13.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
256
257 Unpack the tar file into another area, and test that it
2e550a82 »
2012-04-19 Update step number. Add note.
258 builds and runs properly using the same process in step 8.
259 If there are any problems, fix them and go back to step 8.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
260
4eeffcaa »
2012-07-19 [docs/release_guide.pod] collapsed item numbering
261 =item 14.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
262
16244913 »
2011-09-27 copy release_guide.pod changes from master, renumber for missed 2011.…
263 Tag the release by its release month ("YYYY.MM") and its code name.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
264
16244913 »
2011-09-27 copy release_guide.pod changes from master, renumber for missed 2011.…
265 $ git tag -a -m"tag release #nn" YYYY.MM # e.g., 2010.02
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
266 $ git tag -a -m"tag release #nn" CODENAME # e.g., "Bratislava"
79d0b9a3 »
2009-05-21 Fix "git push --tags" in docs/release_guide.pod .
267 $ git push --tags
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
268
4eeffcaa »
2012-07-19 [docs/release_guide.pod] collapsed item numbering
269 =item 15.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
270
271 Upload the release tarball to github's download area at
01ae3fae »
2009-09-07 [docs] propose ThousandOaks as a release name, in recognition of thei…
272 L<http://github.com/rakudo/rakudo/downloads>.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
273
4eeffcaa »
2012-07-19 [docs/release_guide.pod] collapsed item numbering
274 =item 16.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
275
ecc4efa9 »
2011-04-21 minor modifications
276 To avoid public confusion with Rakudo Star releases, we now publish
ded33e17 »
2010-08-08 Update release guide to note new publication strategy for
277 compiler release announcements ONLY to perl6-compiler@perl.org.
278 (We may restart widespread announcements of compiler releases
279 once they are known, or we may begin publishing a single
280 announcement for both.)
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
281
4eeffcaa »
2012-07-19 [docs/release_guide.pod] collapsed item numbering
282 =item 17.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
283
ecc4efa9 »
2011-04-21 minor modifications
284 Update the Wikipedia entry at L<http://en.wikipedia.org/wiki/Rakudo>.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
285
4eeffcaa »
2012-07-19 [docs/release_guide.pod] collapsed item numbering
286 =item 18.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
287
288 You're done! Celebrate with the appropriate amount of fun.
289
290 =back
381d26ea »
2009-04-22 Updates to docs/announce and docs/release_guide.pod .
291
f45384ae »
2009-02-26 First version of release_guide.pod, based on a proposed version
292 =head1 COPYRIGHT
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
293
63663bd3 »
2012-01-23 correct release date and copyright in release_guide.pod
294 Copyright (C) 2009-2012, The Perl Foundation.
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
295
f45384ae »
2009-02-26 First version of release_guide.pod, based on a proposed version
296 =cut
2f3a8abe »
2009-04-22 Update docs/release_guide.pod with typical steps for cutting a release.
297
f45384ae »
2009-02-26 First version of release_guide.pod, based on a proposed version
298 # Local Variables:
299 # fill-column: 100
300 # End:
301 # vim: expandtab shiftwidth=4:
Something went wrong with that request. Please try again.