Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 304 lines (206 sloc) 9.102 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)
f45384a @pmichaud First version of release_guide.pod, based on a proposed version
pmichaud authored
51
dfd1d7a @moritz update release guide
moritz authored
52 =head2 Planned 2012 releases
f45384a @pmichaud First version of release_guide.pod, based on a proposed version
pmichaud authored
53
54 Dates are based on Parrot's expected release schedule.
55
dfd1d7a @moritz update release guide
moritz authored
56 2012-02-23 #49
57 2012-03-22 #50
58 2012-04-19 #51
59 2012-05-17 #52
60 2012-06-21 #53
f45384a @pmichaud First version of release_guide.pod, based on a proposed version
pmichaud authored
61
381d26e @pmichaud Updates to docs/announce and docs/release_guide.pod .
pmichaud authored
62 =head2 Suggested .pm group names for future releases
63
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
64 MadMongers (YAPC::NA 2012)
65 Brazos Valley (YAPC::NA 2007, p6 hackathon)
381d26e @pmichaud Updates to docs/announce and docs/release_guide.pod .
pmichaud authored
66
1d49284 @perlpilot [docs] Add tentative release dates through the end of 2010
perlpilot authored
67 More names can be gotten from L<http://www.pm.org> if you
68 can't think of one with any particular significance to Perl
03e6f5a @masak [docs/release_guide.pod] slight tweaks
masak authored
69 6 or Rakudo.
1d49284 @perlpilot [docs] Add tentative release dates through the end of 2010
perlpilot authored
70
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
71 =head2 Steps to create a release (for release managers)
72
73 Each Rakudo development release is timed to occur two
01ae3fa @moritz [docs] propose ThousandOaks as a release name, in recognition of thei…
moritz authored
74 days after a Parrot monthly release.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
75
76 =over 4
77
78 =item 1.
79
03e6f5a @masak [docs/release_guide.pod] slight tweaks
masak authored
80 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
81
82 =over 4
83
84 =item *
85
86 Remind people of the upcoming release, invite people to
01ae3fa @moritz [docs] propose ThousandOaks as a release name, in recognition of thei…
moritz authored
87 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
88 release name, etc.
89
90 =item *
91
92 Verify that the Parrot trunk head is able to build Rakudo
e33d20e @moritz [docs] mention smolder reports in release_guide.pod
moritz authored
93 and run the spectest suite. Also check the smolder reports
0d3c66e @moritz [docs] update release guide
moritz authored
94 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
95
96 =item *
97
98 If Parrot's trunk exhibits any problems building or running
99 Rakudo (that require changes to Parrot to fix), immediately
100 report them to the Parrot development team so they can be
101 fixed prior to Parrot's release.
102
103 =item *
104
105 Review the RT queue for tickets that might need resolving
cf27952 [docs] bare bones 2009-08 announcement and release_guide update
Kyle Hasselbacher authored
106 prior to the release, addressing them as needed. "Tickets
107 that need resolving" is left your discretion. Any problem
108 that has a large impact on users is worth addressing either
109 as a fix or as prominent documentation (the README and/or
110 the release announcement).
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
111
112 =back
113
114 =item 2.
115
59332ae @perlpilot update release guide
perlpilot authored
116 Once Parrot issues its monthly release, tag NQP for release
117 according to the year and month of the release:
118
119 $ git clone https://github.com/perl6/nqp.git
120 $ cd nqp
121
122 Follow the steps in NQP's F<docs/release_guide.pod>.
e0bfb29 @moritz [build] git_describe is enough, no need for a separate version specif…
moritz authored
123
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
124 =item 3.
125
01ae3fa @moritz [docs] propose ThousandOaks as a release name, in recognition of thei…
moritz authored
126 The short period following the Parrot release until the
127 Rakudo release is generally intended for fixing bugs,
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
128 updating documentation, and so on.
129
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
130 =item 4.
f3eb64f [release_guide] Added instructions for updating the leap-second tables.
Kodi Arfer authored
131
132 Update Rakudo's leap-second tables:
133
134 $ perl tools/update-tai-utc.pl src/core/tai-utc.pm
135
136 If a new leap second has been announced, F<tai-utc.pm> will be modified, so
137 commit the new version:
138
139 $ git commit src/core/tai-utc.pm
140
141 But probably there won't be any new leap seconds, in which case the file
142 will be unchanged.
143
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
144 =item 5.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
145
146 As the actual release date nears, review the git log history
147 to see if any additional items need to be added to the ChangeLog.
148 This can be conveniently done with "git log --since=yyyy-mm-dd --reverse".
149
48c1791 @pmichaud More release_guide.pod improvements.
pmichaud authored
150 $ git commit docs/ChangeLog
151
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
152 =item 6.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
153
154 When it's time to cut the release, create a new release announcement
9be7890 @pmichaud Update release guide to note that we now use dots instead of hyphens
pmichaud authored
155 in docs/announce/YYYY.MM. It's often a good idea to use the
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
156 previous month's file as a starting point for this. Highlight areas
157 in which the new release is significant. If possible, also give
158 some small details about the choice of release name. (If the
159 details are a bit lengthy, this can often best be done as a separate
160 section at the bottom of the announcement.)
161
082caee @moritz [docs] instruct release manager to include a list of contributors in …
moritz authored
162 Include a list of contributors since the last release in the announcement.
163 You can get an automatically generated list by running
164
cbff7d0 @masak [docs/release_guide.pod] updates and improvements
masak authored
165 $ perl tools/contributors.pl
082caee @moritz [docs] instruct release manager to include a list of contributors in …
moritz authored
166
ecc4efa @perlpilot minor modifications
perlpilot authored
167 B<Note>: this program requires the perl module L<Date::Simple> be installed.
168
082caee @moritz [docs] instruct release manager to include a list of contributors in …
moritz authored
169 Please check the result manually for duplicates and other errors.
170
9be7890 @pmichaud Update release guide to note that we now use dots instead of hyphens
pmichaud authored
171 $ git add docs/announce/YYYY.MM
48c1791 @pmichaud More release_guide.pod improvements.
pmichaud authored
172 $ git commit docs
173
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
174 =item 7.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
175
176 Update the release dates and names at the top of this file
4c248e5 @masak [docs/release_guide.pod] s/-/_/ in file name
masak authored
177 (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
178 you find any steps that are missing.
179
4c248e5 @masak [docs/release_guide.pod] s/-/_/ in file name
masak authored
180 $ git commit docs/release_guide.pod
48c1791 @pmichaud More release_guide.pod improvements.
pmichaud authored
181
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
182 =item 8.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
183
184 Make sure everything compiles and runs from a known clean state:
185
186 $ make realclean
187 $ perl Configure.pl --gen-parrot
188 $ make
189 $ make test
a63c7e0 @moritz add stresstest target, and move day 17 of the advent tests to stresstest
moritz authored
190 $ make stresstest
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
191
674c984 @perlpilot [release] update release_guide
perlpilot authored
192 There are many tests to run for the stresstest target. If
193 you have a machine with multiple CPU cores, you may want to
194 execute that last as
195
196 $ TEST_JOBS=4 make stresstest
197
198 where 4 is the number of CPU cores. This should make the
199 total time to execute all of the tests dramatically less.
200
201 Continue adjusting things until make stresstest passes as expected.
3c7289b @pmichaud Small improvement to guidelines for failing spectests at time of rele…
pmichaud authored
202 Often this means fixing a bug, fudging a test, or (temporarily?)
0d3c66e @moritz [docs] update release guide
moritz authored
203 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
204 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
205
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
206 =item 9.
0d3c66e @moritz [docs] update release guide
moritz authored
207
9cbe751 @moritz update release guide to include tagging of NQP
moritz authored
208 =over 4
209
210 =item *
211
212 Go to the NQP repository, tag it and push the tags
213
214 $ git tag -a -m"tag release YYYY.MM" YYYY.MM # e.g., 2010.02
215
216 Check the NQP revision
217
218 $ git describe # should come out as YYYY.MM
219 # if not, contact your local git vendor or #perl6
220
221 If you got the same version back as you entered, proceed with
222
223 $ git push --tags
224
225 =item *
226
227 Go back to the Rakudo repository, and update the NQP dependency:
228
229 $ echo YYYY.MM > tools/build/NQP_REVISION
230 $ git commit -m '[release] bump NQP revision' tools/build/NQP_REVISION
231
232 =item *
233
0d3c66e @moritz [docs] update release guide
moritz authored
234 Enter the new version into the F<VERSION> file, and commit the changes:
235
236 $ echo 2010.09 > VERSION
237 $ git commit -m '[release] bump VERSION' VERSION
238
9cbe751 @moritz update release guide to include tagging of NQP
moritz authored
239 =back
240
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
241 =item 10.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
242
243 Make sure any locally modified files have been pushed back to github.
244
48c1791 @pmichaud More release_guide.pod improvements.
pmichaud authored
245 $ git status
246 $ git push
247
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
248 =item 11.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
249
cbff7d0 @masak [docs/release_guide.pod] updates and improvements
masak authored
250 Create a tarball by entering C<make release VERSION=YYYY.MM>,
240e2f0 @nunorc Testing commit.
nunorc authored
251 where YYYY.MM is the month for which the release is being made.
f83304d @moritz [docs] markup fix
moritz authored
252 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
253
ecc4efa @perlpilot minor modifications
perlpilot authored
254 B<Caution>: this step removes any untracked files in F<t/spec>.
0d3c66e @moritz [docs] update release guide
moritz authored
255 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
256
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
257 =item 12.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
258
259 Unpack the tar file into another area, and test that it
ecc4efa @perlpilot minor modifications
perlpilot authored
260 builds and runs properly using the same process in step 7.
261 If there are any problems, fix them and go back to step 7.
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 =item 13.
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 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
266
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
267 $ 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
268 $ git tag -a -m"tag release #nn" CODENAME # e.g., "Bratislava"
79d0b9a @pmichaud Fix "git push --tags" in docs/release_guide.pod .
pmichaud authored
269 $ git push --tags
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
270
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
271 =item 14.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
272
273 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
274 L<http://github.com/rakudo/rakudo/downloads>.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
275
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
276 =item 15.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
277
ecc4efa @perlpilot minor modifications
perlpilot authored
278 To avoid public confusion with Rakudo Star releases, we now publish
ded33e1 @pmichaud Update release guide to note new publication strategy for
pmichaud authored
279 compiler release announcements ONLY to perl6-compiler@perl.org.
280 (We may restart widespread announcements of compiler releases
281 once they are known, or we may begin publishing a single
282 announcement for both.)
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
283
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
284 =item 16.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
285
ecc4efa @perlpilot minor modifications
perlpilot authored
286 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
287
1624491 @moritz copy release_guide.pod changes from master, renumber for missed 2011.…
moritz authored
288 =item 17.
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
289
290 You're done! Celebrate with the appropriate amount of fun.
291
292 =back
381d26e @pmichaud Updates to docs/announce and docs/release_guide.pod .
pmichaud authored
293
f45384a @pmichaud First version of release_guide.pod, based on a proposed version
pmichaud authored
294 =head1 COPYRIGHT
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
295
63663bd @moritz correct release date and copyright in release_guide.pod
moritz authored
296 Copyright (C) 2009-2012, The Perl Foundation.
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 =cut
2f3a8ab @pmichaud Update docs/release_guide.pod with typical steps for cutting a release.
pmichaud authored
299
f45384a @pmichaud First version of release_guide.pod, based on a proposed version
pmichaud authored
300 # Local Variables:
301 # fill-column: 100
302 # End:
303 # vim: expandtab shiftwidth=4:
Something went wrong with that request. Please try again.