| 1 | Release Calendar
|
|---|
| 2 | ================
|
|---|
| 3 |
|
|---|
| 4 | Overview
|
|---|
| 5 | --------
|
|---|
| 6 |
|
|---|
| 7 | Mesa provides feature/development and stable releases.
|
|---|
| 8 |
|
|---|
| 9 | The table below lists the date and release manager that is expected to
|
|---|
| 10 | do the specific release.
|
|---|
| 11 |
|
|---|
| 12 | Regular updates will ensure that the schedule for the current and the
|
|---|
| 13 | next two feature releases are shown in the table.
|
|---|
| 14 |
|
|---|
| 15 | In order to keep the whole releasing team up to date with the tools
|
|---|
| 16 | used, best practices and other details, the member in charge of the next
|
|---|
| 17 | feature release will be in constant rotation.
|
|---|
| 18 |
|
|---|
| 19 | The way the release schedule works is explained
|
|---|
| 20 | :ref:`here <schedule>`.
|
|---|
| 21 |
|
|---|
| 22 | Take a look :ref:`here <criteria>` if you'd like to
|
|---|
| 23 | nominate a patch in the next stable release.
|
|---|
| 24 |
|
|---|
| 25 | .. _calendar:
|
|---|
| 26 |
|
|---|
| 27 | Calendar
|
|---|
| 28 | --------
|
|---|
| 29 |
|
|---|
| 30 | .. csv-table:: Calendar
|
|---|
| 31 | :header: "Branch", "Expected date", "Release", "Release manager", "Notes"
|
|---|
| 32 | :file: release-calendar.csv
|
|---|
| 33 | :stub-columns: 1
|
|---|
| 34 | :widths: auto
|
|---|
