mirror of
https://gitee.com/openharmony/third_party_mesa3d
synced 2024-11-27 01:20:36 +00:00
8587e57f12
Restructured text (and markdown) is painful to programatically manipulate, most python parsers are geared towards writing markdown and generating html. I'd like to move the calendar updates to being scripted, as such using csv to store them will be convenient. This also allows us to simplify our scripting that manipulates the table considerably. Acked-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8341>
35 lines
890 B
ReStructuredText
35 lines
890 B
ReStructuredText
Release Calendar
|
|
================
|
|
|
|
Overview
|
|
--------
|
|
|
|
Mesa provides feature/development and stable releases.
|
|
|
|
The table below lists the date and release manager that is expected to
|
|
do the specific release.
|
|
|
|
Regular updates will ensure that the schedule for the current and the
|
|
next two feature releases are shown in the table.
|
|
|
|
In order to keep the whole releasing team up to date with the tools
|
|
used, best practices and other details, the member in charge of the next
|
|
feature release will be in constant rotation.
|
|
|
|
The way the release schedule works is explained
|
|
:ref:`here <schedule>`.
|
|
|
|
Take a look :ref:`here <criteria>` if you'd like to
|
|
nominate a patch in the next stable release.
|
|
|
|
.. _calendar:
|
|
|
|
Calendar
|
|
--------
|
|
|
|
.. csv-table:: Calendar
|
|
:header: "Branch", "Expected date", "Release", "Release manager", "Notes"
|
|
:file: release-calendar.csv
|
|
:stub-columns: 1
|
|
:widths: auto
|