Lines Matching +full:- +full:- +full:no +full:- +full:commit +full:- +full:id
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dt…
4 <meta http-equiv="content-type" content="text/html; charset=utf-8">
22 <li><a href="#pickntest">Cherry-pick and test</a>
24 <li><a href="#prerelease">Pre-release announcement</a>
31 <h1 id="overview">Overview</h1>
38 while the latter have a non-zero one.
45 Mesa 10.1.0 - 10.1 branch, feature
46 Mesa 10.1.4 - 10.1 branch, bugfix
47 Mesa 12.0.0 - 12.0 branch, feature
48 Mesa 12.0.2 - 12.0 branch, bugfix
51 <h1 id="schedule">Release schedule</h1>
61 <li>Initial timeplan available 2-4 weeks before the planned branchpoint (rc1)
62 on the mesa-announce@ mailing list.
63 <li>A <a href="#prerelease">pre-release</a> announcement should be available
64 approximatelly 24 hours before the final (non-rc) release.
71 <li>A <a href="#prerelease">pre-release</a> announcement should be available
82 <h1 id="pickntest">Cherry-picking and testing</h1>
94 <h2>Cherry-picking and build/check testing</h2>
96 <p>Done continuously up-to the <a href="#prerelease">pre-release</a> announcement.</p>
99 As an exception, patches can be applied up-to the last ~1h before the actual
111 <li>Testing with different version of system components - LLVM and others is also
115 Achieved by combination of local ad-hoc scripts and AppVeyor plus Travis-CI,
122 Less often (once or twice), shortly before the pre-release announcement.
126 <li><em>no regressions should be observed for Piglit/dEQP/CTS/Vulkan on Intel platforms</em>
127 <li><em>no regressions should be observed for Piglit using the swrast, softpipe
135 <h1 id="branch">Making a branchpoint</h1>
144 testing is done and there are little to-no issues.
159 git tag -s X.Y-branchpoint -m "Mesa X.Y branchpoint"
160 git checkout -b X.Y
161 git push origin X.Y-branchpoint X.Y
169 Check for rare that there are no distribution breaking changes and revert them
170 if needed. Extremely rare - we had only one case so far (see
171 commit 2ced8eb136528914e1bf4e000dea06a9d53c7e04).
174 Proceed to <a href="#release">release</a> -rc1.
177 <h1 id="prerelease">Pre-release announcement</h1>
214 To: mesa-announce@...
215 Cc: mesa-dev@...
220 - NUMBER queued
221 - NUMBER nominated (outstanding)
222 - and NUMBER rejected patches
230 --------------------------------
236 If you have any questions or suggestions - be that about the current patch
241 -----------------------
245 commit SHA
248 COMMIT SUMMARY
255 commit 990f395e007c3204639daa34efc3049f350ee819
260 (cherry picked from commit 8df581520a823564be0ab5af7dbb7d501b1c9670)
268 -----------------
274 SHA COMMIT SUMMARY
286 COMMIT SUMMARY
296 SHA COMMIT SUMMARY
301 <h1 id="release">Making a new release</h1>
309 Ensure the latest code is available - both in your local master and the
316 <a href="#pickntest">cherry-pick</a> and
317 <a href="#prerelease">pre-announce</a> stages.
321 <li>make distcheck (you can omit this if you're not using --dist below)
331 git clean -fXd; git clean -nxd
336 chmod 755 -fR $__build_root; rm -rf $__build_root
337 mkdir -p $__build_root && cd $__build_root
339 $__mesa_root/autogen.sh --enable-llvm-shared-libs && make -j2 distcheck
342 tar -xaf mesa-$__version.tar.xz && cd mesa-$__version && scons && cd ..
345 rm -rf cd mesa-$__version
346 tar -xaf mesa-$__version.tar.xz && cd mesa-$__version
348 --with-dri-drivers=i965,swrast \
349 --with-gallium-drivers=swrast \
350 --with-vulkan-drivers=intel \
351 --enable-llvm-shared-libs \
352 --enable-gallium-llvm \
353 --enable-glx-tls \
354 --enable-gbm \
355 --enable-egl \
356 --with-egl-platforms=x11,drm,wayland
357 make -j2 && DESTDIR=`pwd`/test make -j6 install
361 glxinfo | egrep -o "Mesa.*"
366 glxinfo | egrep -o "Mesa.*|Gallium.*"
372 glxinfo | egrep -o "Mesa.*|Gallium.*"
382 steam steam://rungameid/570 -vconsole -vulkan
388 Increment the version contained in the file VERSION at Mesa's top-level, then
389 commit this change.
411 log of all commits. In both cases, HTML-formatted lists are printed to stdout
416 Commit these changes and push the branch.
423 <h3>Use the release.sh script from xorg util-macros</h3>
426 Ensure that the mesa git tree is clean via <code>git clean -fXd</code> and
430 ../relative/path/to/release.sh . # append --dist if you've already done distcheck above
441 …tes/X.Y.Z.html to add the sha256sums as availabe in the mesa-X.Y.Z.announce template. Commit this …
451 git cherry-pick -x X.Y~1
452 git cherry-pick -x X.Y
457 docs/index.html to add a news entry. Then commit and push:
461 git commit -as -m "docs: add news item and link release notes for X.Y.Z"
466 <h1 id="announce">Announce the release</h1>
472 <h1 id="website">Update the mesa3d.org website</h1>
484 /home/users/b/br/brianp/mesa-www/htdocs/ with:
492 <h1 id="bugzilla">Update Bugzilla</h1>
498 If there's outstanding action, close the bug referencing the commit ID which