blob: 930de0edef76c7406703891ea4e146e11e43f0c9 [file] [log] [blame]
Emil Velikov2edc29a2016-11-16 18:25:41 +00001<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
2<html lang="en">
3<head>
4 <meta http-equiv="content-type" content="text/html; charset=utf-8">
Emil Velikov028d29b2016-11-28 17:22:15 +00005 <title>Releasing process</title>
Emil Velikov2edc29a2016-11-16 18:25:41 +00006 <link rel="stylesheet" type="text/css" href="mesa.css">
7</head>
8<body>
9
10<div class="header">
11 <h1>The Mesa 3D Graphics Library</h1>
12</div>
13
14<iframe src="contents.html"></iframe>
15<div class="content">
16
Andres Gomeze0f7d252017-03-27 21:48:10 +030017
Emil Velikov2edc29a2016-11-16 18:25:41 +000018<h1>Releasing process</h1>
19
20<ul>
21<li><a href="#overview">Overview</a>
22<li><a href="#schedule">Release schedule</a>
23<li><a href="#pickntest">Cherry-pick and test</a>
24<li><a href="#branch">Making a branchpoint</a>
25<li><a href="#prerelease">Pre-release announcement</a>
26<li><a href="#release">Making a new release</a>
27<li><a href="#announce">Announce the release</a>
28<li><a href="#website">Update the mesa3d.org website</a>
29<li><a href="#bugzilla">Update Bugzilla</a>
30</ul>
31
Andres Gomeze0f7d252017-03-27 21:48:10 +030032
Emil Velikov2edc29a2016-11-16 18:25:41 +000033<h1 id="overview">Overview</h1>
34
35<p>
36This document uses the convention X.Y.Z for the release number with X.Y being
37the stable branch name.
38<br>
39Mesa provides feature and bugfix releases. Former use zero as patch version (Z),
40while the latter have a non-zero one.
41</p>
42
43<p>
44For example:
45</p>
46<pre>
47 Mesa 10.1.0 - 10.1 branch, feature
48 Mesa 10.1.4 - 10.1 branch, bugfix
49 Mesa 12.0.0 - 12.0 branch, feature
50 Mesa 12.0.2 - 12.0 branch, bugfix
51</pre>
52
Andres Gomeze0f7d252017-03-27 21:48:10 +030053
Emil Velikov2edc29a2016-11-16 18:25:41 +000054<h1 id="schedule">Release schedule</h1>
55
56<p>
57Releases should happen on Fridays. Delays can occur although those should be keep
58to a minimum.
Emil Velikove5c24ad2017-04-24 17:22:19 +010059<br>
60See our <a href="release-calendar.html" target="_parent">calendar</a> for the
61date and other details for individual releases.
Emil Velikov2edc29a2016-11-16 18:25:41 +000062</p>
63
64<h2>Feature releases</h2>
65<ul>
Eric Engestrom077879c2017-02-26 23:58:03 +000066<li>Available approximately every three months.
Emil Velikov2edc29a2016-11-16 18:25:41 +000067<li>Initial timeplan available 2-4 weeks before the planned branchpoint (rc1)
68on the mesa-announce@ mailing list.
69<li>A <a href="#prerelease">pre-release</a> announcement should be available
Eric Engestrom077879c2017-02-26 23:58:03 +000070approximately 24 hours before the final (non-rc) release.
Emil Velikov2edc29a2016-11-16 18:25:41 +000071</ul>
72
73<h2>Stable releases</h2>
74<ul>
75<li>Normally available once every two weeks.
76<li>Only the latest branch has releases. See note below.
77<li>A <a href="#prerelease">pre-release</a> announcement should be available
Eric Engestrom077879c2017-02-26 23:58:03 +000078approximately 48 hours before the actual release.
Emil Velikov2edc29a2016-11-16 18:25:41 +000079</ul>
80
81<p>
82Note: There is one or two releases overlap when changing branches. For example:
83<br>
84The final release from the 12.0 series Mesa 12.0.5 will be out around the same
85time (or shortly after) 13.0.1 is out.
86</p>
87
Andres Gomeze0f7d252017-03-27 21:48:10 +030088
Emil Velikov2edc29a2016-11-16 18:25:41 +000089<h1 id="pickntest">Cherry-picking and testing</h1>
90
91<p>
92Commits nominated for the active branch are picked as based on the
93<a href="submittingpatches.html#criteria" target="_parent">criteria</a> as
94described in the same section.
Andres Gomeze0f7d252017-03-27 21:48:10 +030095</p>
Emil Velikov2edc29a2016-11-16 18:25:41 +000096
97<p>
Andres Gomez80587072017-03-27 21:48:11 +030098Nomination happens in the mesa-stable@ mailing list. However,
99maintainer is resposible of checking for forgotten candidates in the
100master branch. This is achieved by a combination of ad-hoc scripts and
101a casual search for terms such as regression, fix, broken and similar.
102</p>
103
104<p>
105Maintainer is also responsible for testing in various possible permutations of
Emil Velikov2edc29a2016-11-16 18:25:41 +0000106the autoconf and scons build.
107</p>
108
109<h2>Cherry-picking and build/check testing</h2>
110
111<p>Done continuously up-to the <a href="#prerelease">pre-release</a> announcement.</p>
112
113<p>
114As an exception, patches can be applied up-to the last ~1h before the actual
115release. This is made <strong>only</strong> with explicit permission/request,
116and the patch <strong>must</strong> be very well contained. Thus it cannot
117affect more than one driver/subsystem.
118</p>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300119
Emil Velikov2edc29a2016-11-16 18:25:41 +0000120<p>
121Currently Ilia Mirkin and AMD devs have requested "permanent" exception.
122</p>
123
Emil Velikov2edc29a2016-11-16 18:25:41 +0000124<ul>
125<li>make distcheck, scons and scons check must pass
126<li>Testing with different version of system components - LLVM and others is also
127performed where possible.
Andres Gomez8a3e33a2017-03-27 21:48:12 +0300128<li>As a general rule, testing with various combinations of configure
129switches, depending on the specific patchset.
Emil Velikov2edc29a2016-11-16 18:25:41 +0000130</ul>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300131
Emil Velikov2edc29a2016-11-16 18:25:41 +0000132<p>
Andres Gomez8a3e33a2017-03-27 21:48:12 +0300133Achieved by combination of local ad-hoc scripts, mingw-w64 cross
134compilation and AppVeyor plus Travis-CI, the latter as part of their
135Github integration.
Emil Velikov2edc29a2016-11-16 18:25:41 +0000136</p>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300137
Emil Velikovccb89e72017-03-15 17:34:26 +0000138<p>
Andres Gomez029d7be2017-05-03 21:14:38 +0300139For Windows related changes, the main contact point is Brian
140Paul. Jose Fonseca can also help as a fallback contact.
141</p>
142
143<p>
Andres Gomez2be0a992017-05-05 12:44:16 +0300144For Android related changes, the main contact is Tapani
145P&auml;lli. Mauro Rossi is collaborating with android-x86 and may
146provide feedback about the build status in that project.
147</p>
148
149<p>
Andres Gomez9c705372017-03-27 21:48:16 +0300150For MacOSX related changes, Jeremy Huddleston Sequoia is currently a
151good contact point.
152</p>
153
154<p>
Emil Velikovccb89e72017-03-15 17:34:26 +0000155<strong>Note:</strong> If a patch in the current queue needs any additional
156fix(es), then they should be squashed together.
157<br>
158The commit messages and the <code>cherry picked from</code> tags must be preserved.
159</p>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300160
Emil Velikovccb89e72017-03-15 17:34:26 +0000161<p>
162This should be noted in the <a href="#prerelease">pre-announce</a> email.
Andres Gomeze0f7d252017-03-27 21:48:10 +0300163</p>
164
Emil Velikovccb89e72017-03-15 17:34:26 +0000165<pre>
166 git show b10859ec41d09c57663a258f43fe57c12332698e
167
168 commit b10859ec41d09c57663a258f43fe57c12332698e
Andres Gomeze0f7d252017-03-27 21:48:10 +0300169 Author: Jonas Pfeil &lt;pfeiljonas@gmx.de&gt;
Emil Velikovccb89e72017-03-15 17:34:26 +0000170 Date: Wed Mar 1 18:11:10 2017 +0100
171
172 ralloc: Make sure ralloc() allocations match malloc()'s alignment.
173
174 The header of ralloc needs to be aligned, because the compiler assumes
175 ...
176
177 (cherry picked from commit cd2b55e536dc806f9358f71db438dd9c246cdb14)
178
179 Squashed with commit:
180
181 ralloc: don't leave out the alignment factor
182
183 Experimentation shows that without alignment factor gcc and clang choose
184 ...
185
186 (cherry picked from commit ff494fe999510ea40e3ed5827e7818550b6de126)
187</pre>
Emil Velikov2edc29a2016-11-16 18:25:41 +0000188
189<h2>Regression/functionality testing</h2>
190
191<p>
192Less often (once or twice), shortly before the pre-release announcement.
193Ensure that testing is redone if Intel devs have requested an exception, as per above.
194</p>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300195
Emil Velikov2edc29a2016-11-16 18:25:41 +0000196<ul>
197<li><em>no regressions should be observed for Piglit/dEQP/CTS/Vulkan on Intel platforms</em>
198<li><em>no regressions should be observed for Piglit using the swrast, softpipe
199and llvmpipe drivers</em>
200</ul>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300201
Emil Velikov2edc29a2016-11-16 18:25:41 +0000202<p>
203Currently testing is performed courtesy of the Intel OTC team and their Jenkins CI setup. Check with the Intel team over IRC how to get things setup.
204</p>
205
Andres Gomezfcdc96d2017-03-27 21:48:13 +0300206<p>
207Installing the built driver from the pre-announced RC branch in the
208system and making some every day's use until the release may be a good
209idea too.
210</p>
211
Emil Velikov2edc29a2016-11-16 18:25:41 +0000212
213<h1 id="branch">Making a branchpoint</h1>
214
215<p>
216A branchpoint is made such that new development can continue in parallel to
217stabilisation and bugfixing.
218</p>
219
220<p>
221Note: Before doing a branch ensure that basic build and <code>make check</code>
222testing is done and there are little to-no issues.
223<br>
224Ideally all of those should be tackled already.
225</p>
226
227<p>
228Check if the version number is going to remain as, alternatively
229<code> git mv docs/relnotes/{current,new}.html </code> as appropriate.
230</p>
231
232<p>
233To setup the branchpoint:
234</p>
235<pre>
236 git checkout master # make sure we're in master first
237 git tag -s X.Y-branchpoint -m "Mesa X.Y branchpoint"
238 git checkout -b X.Y
Emil Velikov0f8afde2017-01-19 15:35:38 +0000239 git checkout master
240 $EDITOR VERSION # bump the version number
241 git commit -as
Emil Velikov1d104f92017-01-26 19:26:13 +0000242 cp docs/relnotes/{X.Y,X.Y+1}.html # copy/create relnotes template
243 git commit -as
Emil Velikov2edc29a2016-11-16 18:25:41 +0000244 git push origin X.Y-branchpoint X.Y
245</pre>
246
247<p>
248Now go to
249<a href="https://bugs.freedesktop.org/editversions.cgi?action=add&amp;product=Mesa" target="_parent">Bugzilla</a> and add the new Mesa version X.Y.
250</p>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300251
Emil Velikov2edc29a2016-11-16 18:25:41 +0000252<p>
Emil Velikov383e8e22017-02-20 19:27:49 +0000253Check that there are no distribution breaking changes and revert them if needed.
254For example: files being overwritten on install, etc. Happens extremely rarely -
255we had only one case so far (see commit 2ced8eb136528914e1bf4e000dea06a9d53c7e04).
Emil Velikov2edc29a2016-11-16 18:25:41 +0000256</p>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300257
Emil Velikov2edc29a2016-11-16 18:25:41 +0000258<p>
259Proceed to <a href="#release">release</a> -rc1.
260</p>
261
Andres Gomeze0f7d252017-03-27 21:48:10 +0300262
Emil Velikov2edc29a2016-11-16 18:25:41 +0000263<h1 id="prerelease">Pre-release announcement</h1>
264
265<p>
266It comes shortly after outstanding patches in the respective branch are pushed.
267Developers can check, in brief, what's the status of their patches. They,
268alongside very early testers, are strongly encouraged to test the branch and
269report any regressions.
270<br>
271It is followed by a brief period (normally 24 or 48 hours) before the actual
272release is made.
273</p>
274
275<h2>Terminology used</h2>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300276
Emil Velikov2edc29a2016-11-16 18:25:41 +0000277<ul><li>Nominated</ul>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300278
Emil Velikov2edc29a2016-11-16 18:25:41 +0000279<p>
280Patch that is nominated but yet to to merged in the patch queue/branch.
281</p>
282
283<ul><li>Queued</ul>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300284
Emil Velikov2edc29a2016-11-16 18:25:41 +0000285<p>
286Patch is in the queue/branch and will feature in the next release.
287Barring reported regressions or objections from developers.
288</p>
289
290<ul><li>Rejected</ul>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300291
Emil Velikov2edc29a2016-11-16 18:25:41 +0000292<p>
293Patch does not fit the
294<a href="submittingpatches.html#criteria" target="_parent">criteria</a> and
295is followed by a brief information.
296<br>
297The release maintainer is human so if you believe you've spotted a mistake do
298let them know.
299</p>
300
301<h2>Format/template</h2>
302<pre>
303Subject: [ANNOUNCE] Mesa X.Y.Z release candidate
304To: mesa-announce@...
305Cc: mesa-dev@...
306
307Hello list,
308
309The candidate for the Mesa X.Y.Z is now available. Currently we have:
310 - NUMBER queued
311 - NUMBER nominated (outstanding)
312 - and NUMBER rejected patches
313
314BRIEF SUMMARY OF CHANGES
315
316Take a look at section "Mesa stable queue" for more information.
317
318
319Testing reports/general approval
320--------------------------------
321Any testing reports (or general approval of the state of the branch) will be
322greatly appreciated.
323
324The plan is to have X.Y.Z this DAY (DATE), around or shortly after TIME.
325
326If you have any questions or suggestions - be that about the current patch
327queue or otherwise, please go ahead.
328
329
330Trivial merge conflicts
331-----------------------
332List of commits where manual intervention was required.
333Keep the authors in the CC list.
334
335commit SHA
336Author: AUTHOR
337
338 COMMIT SUMMARY
339
340 CHERRY PICKED FROM
341
342
343For example:
344
345commit 990f395e007c3204639daa34efc3049f350ee819
346Author: Emil Velikov &lt;emil.velikov@collabora.com&gt;
347
348 anv: automake: cleanup the generated json file during make clean
349
350 (cherry picked from commit 8df581520a823564be0ab5af7dbb7d501b1c9670)
351
352
353Cheers,
354Emil
355
356
357Mesa stable queue
358-----------------
359
360Nominated (NUMBER)
361==================
362
363AUTHOR (NUMBER):
364 SHA COMMIT SUMMARY
365
366For example:
367
368Dave Airlie (1):
369 2de85eb radv: fix texturesamples to handle single sample case
370
371
372Queued (NUMBER)
373===============
374
375AUTHOR (NUMBER):
376 COMMIT SUMMARY
377
Emil Velikovccb89e72017-03-15 17:34:26 +0000378For example:
379
380Jonas Pfeil (1):
381 ralloc: Make sure ralloc() allocations match malloc()'s alignment.
382Squashed with
383 ralloc: don't leave out the alignment factor
Emil Velikov2edc29a2016-11-16 18:25:41 +0000384
385Rejected (NUMBER)
386=================
387
388Rejected (11)
389=============
390
391AUTHOR (NUMBER):
392 SHA COMMIT SUMMARY
393
394Reason: ...
395</pre>
396
Andres Gomeze0f7d252017-03-27 21:48:10 +0300397
Emil Velikov2edc29a2016-11-16 18:25:41 +0000398<h1 id="release">Making a new release</h1>
399
Emil Velikov2edc29a2016-11-16 18:25:41 +0000400<p>
401These are the instructions for making a new Mesa release.
402</p>
403
404<h3>Get latest source files</h3>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300405
Emil Velikov2edc29a2016-11-16 18:25:41 +0000406<p>
407Ensure the latest code is available - both in your local master and the
408relevant branch.
409</p>
410
411<h3>Perform basic testing</h3>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300412
Emil Velikov2edc29a2016-11-16 18:25:41 +0000413<p>
414Most of the testing should already be done during the
415<a href="#pickntest">cherry-pick</a> and
416<a href="#prerelease">pre-announce</a> stages.
Emil Velikov2edc29a2016-11-16 18:25:41 +0000417So we do a quick 'touch test'
Andres Gomeze0f7d252017-03-27 21:48:10 +0300418</p>
419
Emil Velikov2edc29a2016-11-16 18:25:41 +0000420<ul>
421<li>make distcheck (you can omit this if you're not using --dist below)
422<li>scons (from release tarball)
423<li>the produced binaries work
424</ul>
425
426<p>
427Here is one solution that I've been using.
428</p>
429
430<pre>
Emil Velikov0f246602017-09-04 17:08:15 +0100431 # Set MAKEFLAGS if you haven't already
Emil Velikov2edc29a2016-11-16 18:25:41 +0000432 git clean -fXd; git clean -nxd
433 read # quick cross check any outstanding files
Emil Velikovf9959ca2016-11-28 17:18:06 +0000434 export __version=`cat VERSION`
Emil Velikov2edc29a2016-11-16 18:25:41 +0000435 export __mesa_root=../
436 export __build_root=./foo
437 chmod 755 -fR $__build_root; rm -rf $__build_root
438 mkdir -p $__build_root &amp;&amp; cd $__build_root
439
Emil Velikovcf6e6eb2017-09-04 17:19:43 +0100440 # For the native builds - such as distcheck, scons, sanity test, you
441 # may want to specify which LLVM to use:
Andres Gomez8c1d87b2017-07-08 22:59:38 +0300442 # export LLVM_CONFIG=/usr/lib/llvm-3.9/bin/llvm-config
Emil Velikovcf6e6eb2017-09-04 17:19:43 +0100443
444 # Do a full distcheck
Emil Velikov0f246602017-09-04 17:08:15 +0100445 $__mesa_root/autogen.sh &amp;&amp; make distcheck
Emil Velikov2edc29a2016-11-16 18:25:41 +0000446
Emil Velikovf9b18d52017-02-01 08:42:14 +0000447 # Build check the tarballs (scons, linux)
448 tar -xaf mesa-$__version.tar.xz &amp;&amp; cd mesa-$__version
449 scons
450 cd .. &amp;&amp; rm -rf mesa-$__version
451
452 # Build check the tarballs (scons, windows/mingw)
Emil Velikovcf6e6eb2017-09-04 17:19:43 +0100453 # Temporary drop LLVM_CONFIG, unless you have a Windows/mingw one.
454 # save_LLVM_CONFIG=`echo $LLVM_CONFIG`; unset LLVM_CONFIG
Emil Velikovf9b18d52017-02-01 08:42:14 +0000455 tar -xaf mesa-$__version.tar.xz &amp;&amp; cd mesa-$__version
456 scons platform=windows toolchain=crossmingw
457 cd .. &amp;&amp; rm -rf mesa-$__version
Emil Velikov2edc29a2016-11-16 18:25:41 +0000458
459 # Test the automake binaries
Emil Velikovf9959ca2016-11-28 17:18:06 +0000460 tar -xaf mesa-$__version.tar.xz &amp;&amp; cd mesa-$__version
Emil Velikovcf6e6eb2017-09-04 17:19:43 +0100461 # Restore LLVM_CONFIG, if applicable:
462 # export LLVM_CONFIG=`echo $save_LLVM_CONFIG`; unset save_LLVM_CONFIG
Emil Velikov2edc29a2016-11-16 18:25:41 +0000463 ./configure \
464 --with-dri-drivers=i965,swrast \
465 --with-gallium-drivers=swrast \
Emil Velikovf9959ca2016-11-28 17:18:06 +0000466 --with-vulkan-drivers=intel \
Emil Velikov2edc29a2016-11-16 18:25:41 +0000467 --enable-llvm-shared-libs \
Emil Velikovb3b41562017-02-07 15:53:14 +0000468 --enable-llvm \
Emil Velikovf9959ca2016-11-28 17:18:06 +0000469 --enable-glx-tls \
470 --enable-gbm \
471 --enable-egl \
Emil Velikov2d357732017-04-25 16:39:52 +0100472 --with-platforms=x11,drm,wayland,surfaceless
Emil Velikov0f246602017-09-04 17:08:15 +0100473 make &amp;&amp; DESTDIR=`pwd`/test make install
Emil Velikov652e3672017-02-01 09:31:56 +0000474 __glxinfo_cmd='glxinfo 2>&amp;1 | egrep -o "Mesa.*|Gallium.*|.*dri\.so"'
475 __glxgears_cmd='glxgears 2>&amp;1 | grep -v "configuration file"'
476 __es2info_cmd='es2_info 2>&amp;1 | egrep "GL_VERSION|GL_RENDERER|.*dri\.so"'
477 __es2gears_cmd='es2gears_x11 2>&amp;1 | grep -v "configuration file"'
Andres Gomeze6f45562017-07-08 22:59:40 +0300478 test "x$LD_LIBRARY_PATH" != 'x' &amp;&amp; __old_ld="$LD_LIBRARY_PATH"
479 export LD_LIBRARY_PATH=`pwd`/test/usr/local/lib/:"${__old_ld}"
Emil Velikov2edc29a2016-11-16 18:25:41 +0000480 export LIBGL_DRIVERS_PATH=`pwd`/test/usr/local/lib/dri/
Emil Velikovf9959ca2016-11-28 17:18:06 +0000481 export LIBGL_DEBUG=verbose
Emil Velikov652e3672017-02-01 09:31:56 +0000482 eval $__glxinfo_cmd
483 eval $__glxgears_cmd
484 eval $__es2info_cmd
485 eval $__es2gears_cmd
Emil Velikov2edc29a2016-11-16 18:25:41 +0000486 export LIBGL_ALWAYS_SOFTWARE=1
Emil Velikov652e3672017-02-01 09:31:56 +0000487 eval $__glxinfo_cmd
488 eval $__glxgears_cmd
489 eval $__es2info_cmd
490 eval $__es2gears_cmd
Emil Velikov2edc29a2016-11-16 18:25:41 +0000491 export LIBGL_ALWAYS_SOFTWARE=1
492 export GALLIUM_DRIVER=softpipe
Emil Velikov652e3672017-02-01 09:31:56 +0000493 eval $__glxinfo_cmd
494 eval $__glxgears_cmd
495 eval $__es2info_cmd
496 eval $__es2gears_cmd
Emil Velikovf9959ca2016-11-28 17:18:06 +0000497 # Smoke test DOTA2
498 unset LD_LIBRARY_PATH
Andres Gomeze6f45562017-07-08 22:59:40 +0300499 test "x$__old_ld" != 'x' &amp;&amp; export LD_LIBRARY_PATH="$__old_ld" &amp;&amp; unset __old_ld
Emil Velikovf9959ca2016-11-28 17:18:06 +0000500 unset LIBGL_DRIVERS_PATH
501 unset LIBGL_DEBUG
502 unset LIBGL_ALWAYS_SOFTWARE
503 export VK_ICD_FILENAMES=`pwd`/src/intel/vulkan/dev_icd.json
504 steam steam://rungameid/570 -vconsole -vulkan
Emil Velikov2edc29a2016-11-16 18:25:41 +0000505</pre>
506
507<h3>Update version in file VERSION</h3>
508
509<p>
510Increment the version contained in the file VERSION at Mesa's top-level, then
511commit this change.
512</p>
513
514<h3>Create release notes for the new release</h3>
515
516<p>
517Create a new file docs/relnotes/X.Y.Z.html, (follow the style of the previous
518release notes). Note that the sha256sums section of the release notes should
519be empty (TBD) at this point.
520</p>
521
522<p>
523Two scripts are available to help generate portions of the release notes:
Andres Gomeze0f7d252017-03-27 21:48:10 +0300524</p>
Emil Velikov2edc29a2016-11-16 18:25:41 +0000525
526<pre>
527 ./bin/bugzilla_mesa.sh
528 ./bin/shortlog_mesa.sh
529</pre>
530
531<p>
532The first script identifies commits that reference bugzilla bugs and obtains
533the descriptions of those bugs from bugzilla. The second script generates a
534log of all commits. In both cases, HTML-formatted lists are printed to stdout
535to be included in the release notes.
536</p>
537
538<p>
539Commit these changes and push the branch.
540</p>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300541
Emil Velikov2edc29a2016-11-16 18:25:41 +0000542<pre>
543 git push origin HEAD
544</pre>
545
546
Emil Velikov0f988ad2017-03-15 17:34:25 +0000547<h3>Use the release.sh script from xorg <a href="https://cgit.freedesktop.org/xorg/util/modular/">util-modular</a></h3>
Emil Velikov2edc29a2016-11-16 18:25:41 +0000548
549<p>
Emil Velikov79562032017-03-15 17:34:24 +0000550Start the release process.
Emil Velikov2edc29a2016-11-16 18:25:41 +0000551</p>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300552
Emil Velikov2edc29a2016-11-16 18:25:41 +0000553<pre>
Andres Gomez8c1d87b2017-07-08 22:59:38 +0300554 # For the dist/distcheck, you may want to specify which LLVM to use:
555 # export LLVM_CONFIG=/usr/lib/llvm-3.9/bin/llvm-config
Emil Velikov2edc29a2016-11-16 18:25:41 +0000556 ../relative/path/to/release.sh . # append --dist if you've already done distcheck above
557</pre>
558
559<p>
560Pay close attention to the prompts as you might be required to enter your GPG
561and SSH passphrase(s) to sign and upload the files, respectively.
562</p>
563
564<h3>Add the sha256sums to the release notes</h3>
565
566<p>
Eric Engestrom077879c2017-02-26 23:58:03 +0000567Edit docs/relnotes/X.Y.Z.html to add the sha256sums as available in the mesa-X.Y.Z.announce template. Commit this change.
Emil Velikov2edc29a2016-11-16 18:25:41 +0000568</p>
569
570<h3>Back on mesa master, add the new release notes into the tree</h3>
571
572<p>
573Something like the following steps will do the trick:
574</p>
575
576<pre>
577 git cherry-pick -x X.Y~1
578 git cherry-pick -x X.Y
579</pre>
580
581<p>
Andres Gomez80a0c972017-07-08 22:59:41 +0300582Also, edit docs/relnotes.html to add a link to the new release notes,
583edit docs/index.html to add a news entry, and remove the version from
584docs/release-calendar.html. Then commit and push:
Emil Velikov2edc29a2016-11-16 18:25:41 +0000585</p>
586
587<pre>
Andres Gomez80a0c972017-07-08 22:59:41 +0300588 git commit -as -m "docs: update calendar, add news item and link release notes for X.Y.Z"
Emil Velikov2edc29a2016-11-16 18:25:41 +0000589 git push origin master X.Y
590</pre>
591
592
593<h1 id="announce">Announce the release</h1>
Andres Gomeze0f7d252017-03-27 21:48:10 +0300594
Emil Velikov2edc29a2016-11-16 18:25:41 +0000595<p>
596Use the generated template during the releasing process.
597</p>
598
599
600<h1 id="website">Update the mesa3d.org website</h1>
601
602<p>
Emil Velikove280a6b2017-02-10 12:51:22 +0000603As the hosting was moved to freedesktop, git hooks are deployed to update the
604website. Manually check that it is updated 5-10 minutes after the final <code>git push</code>
Emil Velikov2edc29a2016-11-16 18:25:41 +0000605</p>
606
Andres Gomeze0f7d252017-03-27 21:48:10 +0300607
Emil Velikov2edc29a2016-11-16 18:25:41 +0000608<h1 id="bugzilla">Update Bugzilla</h1>
609
610<p>
611Parse through the bugreports as listed in the docs/relnotes/X.Y.Z.html
612document.
613<br>
614If there's outstanding action, close the bug referencing the commit ID which
615addresses the bug and mention the Mesa version that has the fix.
616</p>
617
618<p>
619Note: the above is not applicable to all the reports, so use common sense.
620</p>
621
622
623</div>
624</body>
625</html>