fixed linter warnings

This commit is contained in:
qubedmaiska 2025-09-09 12:05:31 -04:00
parent e93ddb3796
commit 1be6e5f9b9
No known key found for this signature in database
GPG key ID: 204BCE0FD52C0501
36 changed files with 107 additions and 229 deletions

View file

@ -3,8 +3,8 @@ Qubes R3.0 release schedule
===========================
.. list-table::
:widths: 11 11
.. list-table::
:widths: 11 11
:align: center
:header-rows: 1
@ -16,5 +16,4 @@ Qubes R3.0 release schedule
- 3.0-rc3 release
* - 1 Oct 2015
- 3.0 release

View file

@ -5,8 +5,8 @@ Qubes R3.1 release schedule
This schedule is based on :ref:`Version Scheme <developer/releases/version-scheme:release schedule>`.
.. list-table::
:widths: 38 38
.. list-table::
:widths: 38 38
:align: center
:header-rows: 1
@ -24,5 +24,4 @@ This schedule is based on :ref:`Version Scheme <developer/releases/version-schem
- current-testing freeze before 3.1-rc3
* - :strike:`16 Feb 2016` 23 Feb 2016
- 3.1-rc3 release

View file

@ -5,8 +5,8 @@ Qubes R3.2 release schedule
This schedule is based on :ref:`Version Scheme <developer/releases/version-scheme:release schedule>`.
.. list-table::
:widths: 38 38
.. list-table::
:widths: 38 38
:align: center
:header-rows: 1
@ -28,5 +28,3 @@ This schedule is based on :ref:`Version Scheme <developer/releases/version-schem
- 3.2-rc3 release
* - 29 Sep 2016
- 3.2 release

View file

@ -5,8 +5,8 @@ Qubes R4.0 release schedule
This schedule is based on :ref:`Version Scheme <developer/releases/version-scheme:release schedule>`.
.. list-table::
:widths: 88 88
.. list-table::
:widths: 88 88
:align: center
:header-rows: 1
@ -40,5 +40,4 @@ This schedule is based on :ref:`Version Scheme <developer/releases/version-schem
- decide whether 4.0-rc5 is the final 4.0
* - 28 Mar 2018
- final 4.0 release

View file

@ -5,8 +5,8 @@ Qubes R4.1 release schedule
The table below is based on our :ref:`release schedule policy <developer/releases/version-scheme:release schedule>`.
.. list-table::
:widths: 10 10
.. list-table::
:widths: 10 10
:align: center
:header-rows: 1
@ -34,5 +34,4 @@ The table below is based on our :ref:`release schedule policy <developer/release
- decide whether 4.1.0-rc4 is the final 4.1
* - 2022-02-04
- final 4.1.0 release

View file

@ -7,8 +7,8 @@ Qubes R4.2 release schedule
The table below is based on our :ref:`release schedule policy <developer/releases/version-scheme:release schedule>`.
.. list-table::
:widths: 10 10
.. list-table::
:widths: 10 10
:align: center
:header-rows: 1
@ -22,5 +22,4 @@ The table below is based on our :ref:`release schedule policy <developer/release
- 4.2.0-rc3 release
* - 2023-10-13
- 4.2.0-rc4 release

View file

@ -7,8 +7,8 @@ Qubes R4.3 release schedule
The table below is based on our :ref:`release schedule policy <developer/releases/version-scheme:release schedule>`.
.. list-table::
:widths: 10 10
.. list-table::
:widths: 10 10
:align: center
:header-rows: 1
@ -16,5 +16,4 @@ The table below is based on our :ref:`release schedule policy <developer/release
- Stage
* - TBD
- 4.3.0-rc1 release

View file

@ -39,8 +39,8 @@ Each release candidate period is as follows: For the first two weeks, we accept
The next RC is released five weeks after the former. All packages are published in the ``current`` repository, and the cycle starts over. There should always be at least one release candidate before the final release.
.. list-table::
:widths: 26 26
.. list-table::
:widths: 26 26
:align: center
:header-rows: 1
@ -52,7 +52,6 @@ The next RC is released five weeks after the former. All packages are published
- two weeks
* - ``current-testing`` freeze
- one week
Starting with the second cycle (that is, after ``-rc1``), two weeks into the cycle (after the primary bug-reporting period), we decide whether there should be another RC. If, based on the bugs that have been reported, we decide that the latest RC will be designated as the stable release, then we decide on its release date, which should be no more than one week later.
@ -104,4 +103,4 @@ Check installed version
If you want to know which version you are running, for example to report an issue, you can either check in the Qubes Manager menu under ``About > Qubes OS`` or in the file ``/etc/qubes-release`` in dom0. For the latter you can use a command like ``cat /etc/qubes-release`` in a dom0 terminal.
.. |Release cycle| image:: /attachment/doc/release-cycle.png