Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-12-14 23:45:07 -05:00
Code Issues Projects Releases Packages Wiki Activity

Merge branch 'pr/1558'

Browse source
This commit is contained in:
Solène Rapenne 2025-11-23 17:40:56 +01:00
commit 2584e38208
No known key found for this signature in database
GPG key ID: 8CD42DFD57F0A909
9 changed files with 33 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

4
conf.py
View file

@ -162,3 +162,7 @@ rst_epilog = """
:class: no-scaled-link
:alt: Qubes logo icon
"""
# -- -- Options for the nitpicky mode ----------------------------------------
nitpicky = True

2
developer/releases/3_1/schedule.rst
View file

@ -3,7 +3,7 @@ Qubes R3.1 release schedule
===========================
This schedule is based on :ref:`Version Scheme <developer/releases/version-scheme:release schedule>`.
This schedule is based on our :ref:`release-schedule-policy`.
.. list-table::
:widths: 38 38

2
developer/releases/3_2/schedule.rst
View file

@ -3,7 +3,7 @@ Qubes R3.2 release schedule
===========================
This schedule is based on :ref:`Version Scheme <developer/releases/version-scheme:release schedule>`.
This schedule is based on our :ref:`release-schedule-policy`.
.. list-table::
:widths: 38 38

2
developer/releases/4_0/schedule.rst
View file

@ -3,7 +3,7 @@ Qubes R4.0 release schedule
===========================
This schedule is based on :ref:`Version Scheme <developer/releases/version-scheme:release schedule>`.
This schedule is based on our :ref:`release-schedule-policy`.
.. list-table::
:widths: 88 88

2
developer/releases/4_1/schedule.rst
View file

@ -3,7 +3,7 @@ Qubes R4.1 release schedule
===========================
The table below is based on our :ref:`release schedule policy <developer/releases/version-scheme:release schedule>`.
The table below is based on our :ref:`release-schedule-policy`.
.. list-table::
:widths: 10 10

5
developer/releases/4_2/schedule.rst
View file

@ -2,10 +2,7 @@
Qubes R4.2 release schedule
===========================
**Please note:** *This page is still an unfinished draft in progress. It is being updated as Qubes 4.2 development and testing continues.*
The table below is based on our :ref:`release schedule policy <developer/releases/version-scheme:release schedule>`.
The table below is based on our :ref:`release-schedule-policy`.
.. list-table::
:widths: 10 10

16
developer/releases/4_3/schedule.rst
View file

@ -3,9 +3,13 @@ Qubes R4.3 release schedule
===========================
**Please note:** *This page is still an unfinished draft in progress. It is being updated as Qubes 4.3 development and testing continues.*
.. note::
The table below is based on our :ref:`release schedule policy <developer/releases/version-scheme:release schedule>`.
This page is still an **unfinished draft in progress**. It is being updated as Qubes 4.3 development and testing continues.
To get the latest news, check the `news on the main website <https://www.qubes-os.org/news/>`_.
The table below is based on our :ref:`release-schedule-policy`.
.. list-table::
:widths: 10 10
@ -15,9 +19,9 @@ The table below is based on our :ref:`release schedule policy <developer/release
* - Date
- Stage
* - 2025-08-10
- 4.3.0-rc1 release
- `4.3.0-rc1 release <https://www.qubes-os.org/news/2025/08/10/qubes-os-4-3-0-rc1-available-for-testing/>`_
* - 2025-09-19
- 4.3.0-rc2 release
* - 2025-10-20
- 4.3.0-rc3 release
- `4.3.0-rc2 release <https://www.qubes-os.org/news/2025/09/19/qubes-os-4-3-0-rc2-available-for-testing/>`_
A 4.3.0-rc3 release will follow the 4.3.0-rc2.

17
developer/releases/version-scheme.rst
View file

@ -29,15 +29,19 @@ When enough progress has been made, we announce the first stable release, e.g. `
Please see :doc:`issue tracking </introduction/issue-tracking>` for information about how releases are handled in the issue tracker.
Release schedule
----------------
.. _release-schedule-policy:
Release schedule policy
-----------------------
There is no specific schedule for releases other than a general roadmap. When the time comes, we declare a feature freeze, tag ``-rc1``, and release an ISO. From this point on, no new features are accepted, and our schedule begins.
There is **no specific schedule for releases** other than a general roadmap. When the time comes, we declare a feature freeze, tag ``-rc1``, and release an ISO. From this point on, no new features are accepted, and our schedule begins.
Each release candidate period is as follows: For the first two weeks, we accept and assign bug reports to be fixed before the next release candidate. For the next two weeks, we generally focus on fixing assigned bug reports, so issues discovered during this period may be postponed until a later RC. Finally, there is a one week current-testing freeze, during which time no new packages are released, in the hope that they will be installed and tested by wider user base.
Each release candidate period is as follows:
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.
1. For the first two weeks, **we accept and assign bug reports** to be fixed before the next release candidate.
2. For the next two weeks, we generally **focus on fixing assigned bug reports**, so issues discovered during this period may be postponed until a later RC.
3. Finally, there is a one week current-testing freeze, during which time **no new packages are released**, in the hope that they will be installed and tested by wider user base.
.. list-table::
:widths: 26 26
@ -53,9 +57,12 @@ The next RC is released five weeks after the former. All packages are published
* - ``current-testing`` freeze
- one week
The next RC is usually **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.
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.
To get a real life example, check the :doc:`4_1/schedule`.
|Release cycle|
Bug priorities

4
user/advanced-topics/resize-disk-image.rst
View file

@ -28,8 +28,8 @@ In case of template-based qubes, the private storage (the /home directory and us
.. _increasing-the-size-of-disk-images-1:
Increasing the size of Disk Images
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Increasing the size of Disk Images with :program:`qvm-volume`
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^