-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathrelease-checklist.html
186 lines (162 loc) · 6.03 KB
/
release-checklist.html
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
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Release Procedures</title>
</head>
<body bgcolor="#FFFFFF">
<h1 align=center>
Release Procedures</h1>
(Unlabeled items are handled by the Release Manager)
<h2 align=left>
Patch releases (x.y.z, z ≥ 1)
</h2>
<ul>
<li> <i>SCHEDULING</i>
<ul>
<li> Update developer page
<li> Update R-project homepage
<li> Commit webpage changes
<li> Setup crontab for nightly builds and transitions to beta and
RC
<li> Ensure that VERSION-INFO.dcf is updated and sent to CRAN
<li> Notify r-announce and an r-devel lists to give package maintainers
fair warning.
</ul>
<li> <i>START</i> (T-10)
<ul>
<li> <STRONG>CRAN masters:</STRONG> Populate CRAN subdirectory x.y.z, see <a href="./CRAN/Procedures/R_release_procedures.txt">procedures</a>.
<li> (cron) Set version to "x.y.z beta"
<li> Update the NEWS file header from x.y.(z-1) Patched to x.y.z
<li> Recommended packages should be at their versions for release,
preferably by (T-14).
</ul>
<li> <i>CODE FREEZE</i> (T-7)
<ul>
<li> <STRONG>Binary maintainers:</STRONG> Binary
builds should be available now, if not earlier
<li> (cron) Set version to "x.y.z RC"
</ul>
<li> <i>RELEASE</i> (T)
<ul>
<li> (cron) Create final build. This also pushes the sources and
associated files to CRAN and
sets the version to "x.y.z Patched" in the SVN branch.
<li> Update developer page
<li> Update R-project homepage
<li> Commit webpage changes
<li> Calculate md5sums. NEW: Also do SHA-256 (shasum -a 256 * R-3/*)
<li> Notify r-announce list. Include checksums and relevant section of
NEWS.
<li> <STRONG>CRAN masters:</STRONG>
<ul>
<li>Update CRAN web pages (banner.html, sources.html) by running the "CRAN-homepage-process-templates" script
<li> build manuals (currently not automatically) and push to CRAN
</ul>
</ul>
</ul>
<h2 align=left>
Dot-zero releases (x.y.0)
</h2>
<ul>
<li> <i>SCHEDULING</i>
<ul>
<li> Update developer page
<li> Update R-project homepage
<li> Commit webpage changes
<li> Notify r-announce and r-devel lists
<li> Ensure that VERSION-INFO.dcf is updated and sent to CRAN
</ul>
<li> <i>START</i> (T-31)
<ul>
<li> <STRONG>CRAN masters:</STRONG>
Create and populate CRAN subdirectory src/contrib/x.(y+1).0/Recommended, see <a href="./CRAN/Procedures/R_release_procedures.txt">procedures</a>.
<li> <STRONG>Binaries masters:</STRONG>
Create CRAN subdirectory bin/windows/contrib/x.(y+1).0 etc
<li> Setup crontab for nightly builds and transitions to alpha, beta, and RC
status
</ul>
<li> <i>GRAND-FEATURE FREEZE</i> (T-28)
<ul>
<li> (cron) Run the R-create-branch script, which does the following.
<ul>
<li> Create the SVN release branch
<li> Set VERSION of SVN trunk to "x.(y+1).0 Under development (unstable)"
<li> Set VERSION in release branch to "x.y.0 alpha"
</ul>
<li> <STRONG>CRAN masters:</STRONG> Update devel version in CRAN-package-list
<li> <STRONG>CRAN incoming checkers:</STRONG> Populate user library as
necessary.
<li> Check src/library/tools/R/utils.R for Bioconductor version
matching this release
<li> <STRONG>Translation master:</STRONG> Ask translators for updates by FF
<li> <STRONG>Binary maintainers:</STRONG> Start publishing binary builds
<li> <STRONG>Binary package maintainers:</STRONG>
<ul>
<li> Create package directories x.y and x.(y+1)
<li> Update package testing environment
<li> Send automated
messages to maintainers whose packages are failing.
</ul>
</ul>
<li> <i>FEATURE FREEZE</i> (T-14)
<ul>
<li> (cron) Set VERSION in release branch to "x.y.0 beta"
<li> Recommended packages should be at their versions for release
(since changes to one can affect another).
</ul>
<li> <i>CODE FREEZE</i> (T-7)
<ul>
<li> (cron) Set VERSION in release branch to "x.y.0 RC"
</ul>
<li> <i>PRERELEASE</i> (T-3)
<ul>
<li> <STRONG>CRAN masters:</STRONG> Populate CRAN subdirectory x.y-patched, see <a href="./CRAN/Procedures/R_release_procedures.txt">procedures</a>.
</ul>
<li> <i>RELEASE</i> (T)
<ul>
<li> (cron) Create final build. This also pushes the sources and
associated files to CRAN and
sets the version to "x.y.z Patched" in the SVN branch.
<li> Update developer page
<li> Update R-project homepage
<li> Commit webpage changes
<li> Calculate md5sums and SHA-256
<li> Notify r-announce list. Include checksums and relevant section of
NEWS.
<li> <STRONG>CRAN masters:</STRONG>
<ul>
<li> Update CRAN web pages (banner.html, sources.html) by running the "CRAN-homepage-process-templates" script
<li> update links (r-oldrel, r-release, r-devel, ...)
<li> build manuals (currently not automatically) and push to CRAN
</ul>
</ul>
</ul>
<STRONG>TODO:</STRONG> Unresolved/unautomated items. (I.e., someone usually remembers to do it.)
<ul>
<li> Update <tt>.save</tt> files (notably <tt>internet.Rout.save</tt>).
<li> Update reference to BioC versions. (This needs the BioC
maintainers to have set up <strong>all three</strong> BioC repositories for the
development version. Nowadays done not later than GFF.)
<li> Relabeling inside NEWS.
<li> Update bug repository settings, so that people can report on new versions.
<li> Update <tt>tools/config.{guess,sub}</tt> from the git URLs given
within them. (These are GPL-3 but with an exception.)
<li> Update software included under <tt>src/extra</tt>:
<ul>
<li> <a href="http://laurikari.net/tre/download/">tre</a>
<li> <a href="http://sourceforge.net/projects/ctrio/files/">trio</a>:
only used on Windows.
<li> <a href="http://www.iana.org/time-zones">tzone</a>: this
amounts to picking up the latest <tt>tzdata</tt> file, and on a
machine with a fully 64-bit <tt>zic</tt> (usually Linux, not OS X)
following the procedure in <tt>src/extra/tzone/Notes</tt>.
<li> <a href="https://github.com/win-iconv/win-iconv">win_iconv</a>:
only used on Windows.
</ul>
<p>
We don't update <tt>intl</tt> (originally for licence reasons, but
it reverted to LGPL 2.1).
</ul>
</body>
</html>