Lines Matching defs:release
7 This document uses the convention X.Y.Z for the release number with X.Y
30 See our :doc:`calendar <release-calendar>` for information about how
31 the release schedule is planned, and the date and other details for
42 - Typically, the final release will happen after 4 candidates.
57 The final release from the 12.0 series Mesa 12.0.5 will be out around
60 This also involves that, as a final release may be delayed due to the
62 release manager might have to update the
63 :doc:`calendar <release-calendar>` with additional bug fix releases of
88 the last one hour before the actual release. This is made **only** with
204 Making a new release
207 These are the instructions for making a new Mesa release.
261 Create release notes for the new release
264 The release notes are completely generated by the
271 this, ``release.sh`` below will fail).
273 Use the release.sh script from xorg `util-modular <https://cgit.freedesktop.org/xorg/util/modular/>`__
276 Start the release process.
280 ../relative/path/to/release.sh . # append --dist if you've already done distcheck above
287 release notes, and is published in `release-maintainers-keys.asc
288 <release-maintainers-keys.asc>`__.
291 Add the sha256sums to the release notes
297 Back on mesa main, add the new release notes into the tree
314 docs/relnotes.rst and docs/release-calendar.csv. It will then generate
322 Announce the release
327 Again, pay attention to add a note to warn about a final release in a