Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 302 lines (211 sloc) 9.641 kB
f45384a @pmichaud First version of release_guide.pod, based on a proposed version
pmichaud authored
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
5b477c0 @pmichaud Note the release manager for each of the previous releases,
pmichaud authored
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)
cf27952 [docs] bare bones 2009-08 announcement and release_guide update
Kyle Hasselbacher authored
21 2009-08-20 Rakudo #20 "PDX" (kyle)
e33d20e @moritz [docs] mention smolder reports in release_guide.pod
moritz authored
22 2009-09-17 Rakudo #21 "Seattle" (particle)
37956bf @perlpilot Updates in preparation for release
perlpilot authored
23 2009-10-22 Rakudo #22 "Thousand Oaks" (duff)
f5065b6 @masak [docs/release_guide.pod] rolled releases forward
masak authored
24 2009-11-19 Rakudo #23 "Lisbon" (masak)
7f1c3fe @chromatic [docs] Updated release guide.
chromatic authored
25 2009-12-17 Rakudo #24 "Seoul" (chromatic)
4da4e4d @pmichaud Update release dates and names.
pmichaud authored
26 2010-01-22 Rakudo #25 "Minneapolis" (pmichaud)
37e5746 @pmichaud Update release_guide.pod with recent release information.
pmichaud authored
27 2010-02-18 Rakudo #26 "Amsterdam" (mberends)
fc30fad @moritz [docs] the Copenhagen release has already happend; colomon++ voluntue…
moritz authored
28 2010-03-18 Rakudo #27 "Copenhagen" (smash)
05ee824 @moritz [docs] update release guide
moritz authored
29 2010-04-22 Rakudo #28 "Moscow" (moritz)
296a56c @colomon Add #29 Erlangen to the release list, and mark that [Coke] has the Ju…
colomon authored
30 2010-05-20 Rakudo #29 "Erlangen" (colomon)
cbff7d0 @masak [docs/release_guide.pod] updates and improvements
masak authored
31 2010-06-17 Rakudo #30 "Kiev" (masak)
5c33c5a @coke This release is heading out the door soon.
coke authored
32 2010-07-22 Rakudo #31 "Atlanta" (Coke)
99a4e24 @mathw Update release guide with 2010.08 release.
mathw authored
33 2010-08-19 Rakudo #32 "Pisa" (mathw)
74a156f @moritz [release] name is Milan. Bump VERSION
moritz authored
34 2010-09-23 Rakudo #33 "Milan" (moritz)
33bdcee @perlpilot release preparation
perlpilot authored
35 2010-10-21 Rakudo #34 "Paris" (duff)
03e6f5a @masak [docs/release_guide.pod] slight tweaks
masak authored
36 2010-11-18 Rakudo #35 "Melbourne" (masak)
4830af6 @nunorc [release] update release guide
nunorc authored
37 2010-12-23 Rakudo #36 "New York" (smash)
a7d5f19 @tadzik Added announcement for 2011.01
tadzik authored
38 2011-01-20 Rakudo #37 "BristolBath" (tadzik)
c25afe6 @arnsholt [release] Add announcement, updated release guide. Added own name and
arnsholt authored
39 2011-02-17 Rakudo #38 "Toulouse" (arnsholt)
e70f27d @jdhore [release] Add announcement, update release gude and add myself to
jdhore authored
40 2011-03-17 Rakudo #39 "Orlando" (jdhore)
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
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 --
01d3a6b @perlpilot Update release info
perlpilot authored
46 2011-09-30 Rakudo #44 "Riga" (tadzik)
e17c139 @perlpilot Choose a release name
perlpilot authored
47 2011-10-20 Rakudo #45 "Houston" (duff)
617fef9 @tadzik Add a new release announcement, update release_guide
tadzik authored
48 2011-11-17 Rakudo #46 "London" (tadzik)
dfd1d7a @moritz update release guide
moritz authored
49 2011-12-22 Rakudo #47 "Columbus" (moritz)
63663bd @moritz correct release date and copyright in release_guide.pod
moritz authored
50 2012-01-23 Rakudo #48 "Toronto" (moritz)
a95379d @masak [docs/release_guide.pod] updated
masak authored
51 2012-02-23 Rakudo #49 "SPb" (masak)
5dda9a7 @masak [docs/release_guide.doc] current release => past
masak authored
52 2012-03-22 Rakudo #50 "Argentina" (masak)
65ab8e3 @coke nearly done planning...
coke authored
53 2012-04-19 Rakudo #51 "Brazos Valley" (Coke)
5a65af3 @moritz add 2012.04 release to release_guide.pod
moritz authored
54 2012-04-25 2012.04.1 (moritz)
8004748 @tadzik Update release guide
tadzik authored
55 2012-05-17 Rakudo #52 "MadMongers" (tadzik)
29607d8 @perlpilot update release announcement
perlpilot authored
56 2012-06-21 Rakudo #53 "Strasbourg" (duff)
9fb677f @masak [docs/release_guide.pod] named current release
masak authored
57 2012-07-19 Rakudo #54 "Tallinn" (masak)
f45384a @pmichaud First version of release_guide.pod, based on a proposed version
pmichaud authored
58
dfd1d7a @moritz update release guide
moritz authored
59 =head2 Planned 2012 releases
f45384a @pmichaud First version of release_guide.pod, based on a proposed version
pmichaud authored
60
61 Dates are based on Parrot's expected release schedule.
62
8004748 @tadzik Update release guide
tadzik authored
63 2012-08-23 Rakudo #55 tadzik
5dda9a7 @masak [docs/release_guide.doc] current release => past
masak authored
64 2012-09-20 Rakudo #56
6bee9b6 @perlpilot [docs/release_guide.pod] claim birthday month release too
perlpilot authored
65 2012-10-18 Rakudo #57 duff
5dda9a7 @masak [docs/release_guide.doc] current release => past
masak authored
66 2012-11-22 Rakudo #58
67 2012-12-20 Rakudo #59
f45384a @pmichaud First version of release_guide.pod, based on a proposed version
pmichaud authored
68
381d26e @pmichaud Updates to docs/announce and docs/release_guide.pod .
pmichaud authored
69 =head2 Suggested .pm group names for future releases
70
1d49284 @perlpilot [docs] Add tentative release dates through the end of 2010
perlpilot authored
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
03e6f5a @masak [docs/release_guide.pod] slight tweaks
masak authored
73 6 or Rakudo.
1d49284 @perlpilot [docs] Add tentative release dates through the end of 2010
perlpilot authored
74
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
75 =head2 Steps to create a release (for release managers)
76
77 Each Rakudo development release is timed to occur two
01ae3fa @moritz [docs] propose ThousandOaks as a release name, in recognition of thei…
moritz authored
78 days after a Parrot monthly release.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
79
80 =over 4
81
82 =item 1.
83
03e6f5a @masak [docs/release_guide.pod] slight tweaks
masak authored
84 A few days before the Parrot release, it's a good idea to...
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
85
86 =over 4
87
88 =item *
89
90 Remind people of the upcoming release, invite people to
01ae3fa @moritz [docs] propose ThousandOaks as a release name, in recognition of thei…
moritz authored
91 update the ChangeLog file, update the ROADMAP, choose a
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
92 release name, etc.
93
94 =item *
95
d90f671 @moritz [release_guide] remove SVNisms
moritz authored
96 Verify that the Parrot master branch is able to build Rakudo
e33d20e @moritz [docs] mention smolder reports in release_guide.pod
moritz authored
97 and run the spectest suite. Also check the smolder reports
0d3c66e @moritz [docs] update release guide
moritz authored
98 at L<http://smolder.parrot.org/app/projects/smoke_reports/5>.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
99
100 =item *
101
d90f671 @moritz [release_guide] remove SVNisms
moritz authored
102 If Parrot's master branch exhibits any problems building or running
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
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
cf27952 [docs] bare bones 2009-08 announcement and release_guide update
Kyle Hasselbacher authored
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).
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
115
115ab2f @pmichaud Move "create release announcement" into step 1.
pmichaud authored
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
5ae28cc @pmichaud [release-guide.pod]: Add note to update README copyright date.
pmichaud authored
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
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
134 =back
135
136 =item 2.
137
01ae3fa @moritz [docs] propose ThousandOaks as a release name, in recognition of thei…
moritz authored
138 The short period following the Parrot release until the
139 Rakudo release is generally intended for fixing bugs,
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
140 updating documentation, and so on.
141
4b2c1fe @moritz [release_guide] remove redundancy with nqp's release guide
moritz authored
142 =item 3.
f3eb64f [release_guide] Added instructions for updating the leap-second tables.
Kodi Arfer authored
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
96ab007 @coke Add note about script requirement
coke authored
156 B<Note>: this program requires the perl module L<Time::y2038> be installed.
157
4b2c1fe @moritz [release_guide] remove redundancy with nqp's release guide
moritz authored
158 =item 4.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
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
48c1791 @pmichaud More release_guide.pod improvements.
pmichaud authored
164 $ git commit docs/ChangeLog
165
4b2c1fe @moritz [release_guide] remove redundancy with nqp's release guide
moritz authored
166 =item 5.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
167
115ab2f @pmichaud Move "create release announcement" into step 1.
pmichaud authored
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
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
174 section at the bottom of the announcement.)
175
082caee @moritz [docs] instruct release manager to include a list of contributors in …
moritz authored
176 Include a list of contributors since the last release in the announcement.
177 You can get an automatically generated list by running
178
cbff7d0 @masak [docs/release_guide.pod] updates and improvements
masak authored
179 $ perl tools/contributors.pl
082caee @moritz [docs] instruct release manager to include a list of contributors in …
moritz authored
180
ecc4efa @perlpilot minor modifications
perlpilot authored
181 B<Note>: this program requires the perl module L<Date::Simple> be installed.
182
082caee @moritz [docs] instruct release manager to include a list of contributors in …
moritz authored
183 Please check the result manually for duplicates and other errors.
184
9be7890 @pmichaud Update release guide to note that we now use dots instead of hyphens
pmichaud authored
185 $ git add docs/announce/YYYY.MM
48c1791 @pmichaud More release_guide.pod improvements.
pmichaud authored
186 $ git commit docs
187
4eeffca @masak [docs/release_guide.pod] collapsed item numbering
masak authored
188 =item 6.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
189
190 Update the release dates and names at the top of this file
4c248e5 @masak [docs/release_guide.pod] s/-/_/ in file name
masak authored
191 (F<docs/release_guide.pod>). Also improve these instructions if
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
192 you find any steps that are missing.
193
4c248e5 @masak [docs/release_guide.pod] s/-/_/ in file name
masak authored
194 $ git commit docs/release_guide.pod
48c1791 @pmichaud More release_guide.pod improvements.
pmichaud authored
195
4eeffca @masak [docs/release_guide.pod] collapsed item numbering
masak authored
196 =item 7.
5921c70 @pmichaud Move the "make sure everything compiles/runs" testing step to _after_…
pmichaud authored
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
4eeffca @masak [docs/release_guide.pod] collapsed item numbering
masak authored
201 =item 8.
5921c70 @pmichaud Move the "make sure everything compiles/runs" testing step to _after_…
pmichaud authored
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
4eeffca @masak [docs/release_guide.pod] collapsed item numbering
masak authored
208 =item 9.
5921c70 @pmichaud Move the "make sure everything compiles/runs" testing step to _after_…
pmichaud authored
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
4eeffca @masak [docs/release_guide.pod] collapsed item numbering
masak authored
215 =item 10.
5921c70 @pmichaud Move the "make sure everything compiles/runs" testing step to _after_…
pmichaud authored
216
217 Make sure any locally modified files have been pushed back to github.
218
219 $ git status
220 $ git push
221
4eeffca @masak [docs/release_guide.pod] collapsed item numbering
masak authored
222 =item 11.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
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
a63c7e0 @moritz add stresstest target, and move day 17 of the advent tests to stresstest
moritz authored
230 $ make stresstest
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
231
674c984 @perlpilot [release] update release_guide
perlpilot authored
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.
3c7289b @pmichaud Small improvement to guidelines for failing spectests at time of rele…
pmichaud authored
242 Often this means fixing a bug, fudging a test, or (temporarily?)
0d3c66e @moritz [docs] update release guide
moritz authored
243 commenting out a test file in t/spectest.data . Use your best
3c7289b @pmichaud Small improvement to guidelines for failing spectests at time of rele…
pmichaud authored
244 judgment or ask others if uncertain what to do here.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
245
4eeffca @masak [docs/release_guide.pod] collapsed item numbering
masak authored
246 =item 12.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
247
cbff7d0 @masak [docs/release_guide.pod] updates and improvements
masak authored
248 Create a tarball by entering C<make release VERSION=YYYY.MM>,
240e2f0 @nunorc Testing commit.
nunorc authored
249 where YYYY.MM is the month for which the release is being made.
f83304d @moritz [docs] markup fix
moritz authored
250 This will create a tarball file named C<rakudo-YYYY.MM.tar.gz>.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
251
ecc4efa @perlpilot minor modifications
perlpilot authored
252 B<Caution>: this step removes any untracked files in F<t/spec>.
0d3c66e @moritz [docs] update release guide
moritz authored
253 So please make a backup if you have any important data in there.
e3fe329 @moritz [docs] warn about potential damage from "make release"
moritz authored
254
4eeffca @masak [docs/release_guide.pod] collapsed item numbering
masak authored
255 =item 13.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
256
257 Unpack the tar file into another area, and test that it
2e550a8 @coke Update step number. Add note.
coke authored
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.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
260
4eeffca @masak [docs/release_guide.pod] collapsed item numbering
masak authored
261 =item 14.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
262
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
263 Tag the release by its release month ("YYYY.MM") and its code name.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
264
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
265 $ git tag -a -m"tag release #nn" YYYY.MM # e.g., 2010.02
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
266 $ git tag -a -m"tag release #nn" CODENAME # e.g., "Bratislava"
79d0b9a @pmichaud Fix "git push --tags" in docs/release_guide.pod .
pmichaud authored
267 $ git push --tags
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
268
4eeffca @masak [docs/release_guide.pod] collapsed item numbering
masak authored
269 =item 15.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
270
271 Upload the release tarball to github's download area at
01ae3fa @moritz [docs] propose ThousandOaks as a release name, in recognition of thei…
moritz authored
272 L<http://github.com/rakudo/rakudo/downloads>.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
273
4eeffca @masak [docs/release_guide.pod] collapsed item numbering
masak authored
274 =item 16.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
275
ecc4efa @perlpilot minor modifications
perlpilot authored
276 To avoid public confusion with Rakudo Star releases, we now publish
ded33e1 @pmichaud Update release guide to note new publication strategy for
pmichaud authored
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.)
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
281
4eeffca @masak [docs/release_guide.pod] collapsed item numbering
masak authored
282 =item 17.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
283
ecc4efa @perlpilot minor modifications
perlpilot authored
284 Update the Wikipedia entry at L<http://en.wikipedia.org/wiki/Rakudo>.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
285
4eeffca @masak [docs/release_guide.pod] collapsed item numbering
masak authored
286 =item 18.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
287
288 You're done! Celebrate with the appropriate amount of fun.
289
290 =back
381d26e @pmichaud Updates to docs/announce and docs/release_guide.pod .
pmichaud authored
291
f45384a @pmichaud First version of release_guide.pod, based on a proposed version
pmichaud authored
292 =head1 COPYRIGHT
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
293
63663bd @moritz correct release date and copyright in release_guide.pod
moritz authored
294 Copyright (C) 2009-2012, The Perl Foundation.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
295
f45384a @pmichaud First version of release_guide.pod, based on a proposed version
pmichaud authored
296 =cut
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
297
f45384a @pmichaud First version of release_guide.pod, based on a proposed version
pmichaud authored
298 # Local Variables:
299 # fill-column: 100
300 # End:
301 # vim: expandtab shiftwidth=4:
Something went wrong with that request. Please try again.