diff --git a/conf.py b/conf.py index dff9062e..d4e4eebe 100644 --- a/conf.py +++ b/conf.py @@ -162,3 +162,7 @@ rst_epilog = """ :class: no-scaled-link :alt: Qubes logo icon """ + +# -- -- Options for the nitpicky mode ---------------------------------------- + +nitpicky = True diff --git a/developer/releases/3_1/schedule.rst b/developer/releases/3_1/schedule.rst index 30f7c21c..63592e1d 100644 --- a/developer/releases/3_1/schedule.rst +++ b/developer/releases/3_1/schedule.rst @@ -3,7 +3,7 @@ Qubes R3.1 release schedule =========================== -This schedule is based on :ref:`Version Scheme `. +This schedule is based on our :ref:`release-schedule-policy`. .. list-table:: :widths: 38 38 diff --git a/developer/releases/3_2/schedule.rst b/developer/releases/3_2/schedule.rst index 5304b148..8bb58562 100644 --- a/developer/releases/3_2/schedule.rst +++ b/developer/releases/3_2/schedule.rst @@ -3,7 +3,7 @@ Qubes R3.2 release schedule =========================== -This schedule is based on :ref:`Version Scheme `. +This schedule is based on our :ref:`release-schedule-policy`. .. list-table:: :widths: 38 38 diff --git a/developer/releases/4_0/schedule.rst b/developer/releases/4_0/schedule.rst index 9a7d4e0f..9f0a6a88 100644 --- a/developer/releases/4_0/schedule.rst +++ b/developer/releases/4_0/schedule.rst @@ -3,7 +3,7 @@ Qubes R4.0 release schedule =========================== -This schedule is based on :ref:`Version Scheme `. +This schedule is based on our :ref:`release-schedule-policy`. .. list-table:: :widths: 88 88 diff --git a/developer/releases/4_1/schedule.rst b/developer/releases/4_1/schedule.rst index e88b645d..2a56afd0 100644 --- a/developer/releases/4_1/schedule.rst +++ b/developer/releases/4_1/schedule.rst @@ -3,7 +3,7 @@ Qubes R4.1 release schedule =========================== -The table below is based on our :ref:`release schedule policy `. +The table below is based on our :ref:`release-schedule-policy`. .. list-table:: :widths: 10 10 diff --git a/developer/releases/4_2/schedule.rst b/developer/releases/4_2/schedule.rst index daaa7ace..63c2dea0 100644 --- a/developer/releases/4_2/schedule.rst +++ b/developer/releases/4_2/schedule.rst @@ -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 `. +The table below is based on our :ref:`release-schedule-policy`. .. list-table:: :widths: 10 10 diff --git a/developer/releases/4_3/schedule.rst b/developer/releases/4_3/schedule.rst index e1305170..7a36108f 100644 --- a/developer/releases/4_3/schedule.rst +++ b/developer/releases/4_3/schedule.rst @@ -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 `. + 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 `_. + +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 `_ * - 2025-09-19 - - 4.3.0-rc2 release - * - 2025-10-20 - - 4.3.0-rc3 release + - `4.3.0-rc2 release `_ + +A 4.3.0-rc3 release will follow the 4.3.0-rc2. diff --git a/developer/releases/version-scheme.rst b/developer/releases/version-scheme.rst index e88c9cfb..25122d6d 100644 --- a/developer/releases/version-scheme.rst +++ b/developer/releases/version-scheme.rst @@ -29,15 +29,19 @@ When enough progress has been made, we announce the first stable release, e.g. ` Please see :doc:`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 diff --git a/user/advanced-topics/resize-disk-image.rst b/user/advanced-topics/resize-disk-image.rst index 5dcdc36a..f6fee872 100644 --- a/user/advanced-topics/resize-disk-image.rst +++ b/user/advanced-topics/resize-disk-image.rst @@ -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` +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^