mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-08-11 16:10:45 -04:00
Convert to RST
This is done using tools at https://github.com/maiska/qubes-translation-utilz, commit 4c8e2a7f559fd37e29b51769ed1ab1c6cf92e00d.
This commit is contained in:
Marek Marczykowski-Górecki
parent
e3db139fe3
commit
7e464d0f40
428 changed files with 32833 additions and 29703 deletions
|
|
@ -1,50 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/1.0/release-notes/
|
||||
redirect_from:
|
||||
- /en/doc/releases/1.0/release-notes/
|
||||
ref: 18
|
||||
title: Qubes R1.0 release notes
|
||||
---
|
||||
|
||||
Detailed release notes in [this blog post](https://blog.invisiblethings.org/2012/09/03/introducing-qubes-10.html).
|
||||
|
||||
## Known issues
|
||||
|
||||
- Installer might not support some USB keyboards (\#230). This seems to include all the Mac Book keyboards (most PC laptops have PS2 keyboards and are not affected).
|
||||
|
||||
- If you don't enable Composition (System Setting -\> Desktop -\> Enable desktop effects), which you really should do, then the KDE task bar might get ugly (e.g. half of it might be black). This is some KDE bug that we don't plan to fix.
|
||||
|
||||
- Some keyboard layout set by KDE System Settings can cause [keyboard not working at all](https://groups.google.com/group/qubes-devel/browse_thread/thread/77d076b65dda7226). If you hit this issue, you can switch to console (by console login option) and manually edit `/etc/X11/xorg.conf.d/00-system-setup-keyboard.conf` (and `/etc/sysconfig/keyboard`) and place correct keyboard layout settings (details in linked thread). You can check if specific keyboard layout settings are proper using `setxkbmap` tool.
|
||||
|
||||
- On systems with more than 8GB of RAM there is problem with DisposableVM. To fix it, limit maximum memory allocation for DispVM to 3GB
|
||||
|
||||
~~~
|
||||
qvm-prefs -s fedora-17-x64-dvm maxmem 3072
|
||||
qvm-create-default-dvm --default-template --default-script
|
||||
~~~
|
||||
|
||||
- On some systems the KDE Window Manager might freeze upon resuming from S3 sleep when compositing is enabled (and the only method to log in to the system if this happens is to switch to a text console, enter your user's password, kill the kwin process, go back to the Xorg console, log in, and start a new instance of kwin using Konsole application :) If you experience such problems, make sure to disable compositing before putting the system into sleep by pressing Alt-Ctrl-F12 (and then enabling it back once you log in after resume) -- this way you should never see this problem again.
|
||||
|
||||
## Downloads
|
||||
|
||||
See [Qubes Downloads](/doc/QubesDownloads/).
|
||||
|
||||
## Installation instructions
|
||||
|
||||
See [Installation Guide](/doc/installation-guide/).
|
||||
|
||||
## Upgrading
|
||||
|
||||
### From Qubes 1.0-rc1
|
||||
|
||||
If you're already running Qubes 1.0-rc1, you don't need to reinstall, it's just enough to update the packages in your Dom0 and the template VM(s). The easiest way for doing this is to click on the Update Button in the Qubes Manger -- one click when you selected Dom0, and one click for each of your template VM (by default there is just one template).
|
||||
|
||||
### From Qubes 1.0 Beta 3
|
||||
|
||||
If you have Qubes Beta 3 currently installed on your system, you must reinstall from scratch, as we offer no direct upgrade option in the installer (sorry). However, we do offer tools for smooth migration of your AppVMs. In order to do that, please backup your AppVMs using the `qvm-backup` tool [as usual](/doc/backup-restore/). Then, after you install Qubes 1.0 rc1, you can restore them using `qvm-backup-restore` tool. However, because we have changed the default template in RC1, you should tell qvm-back-restore about that by passing `--replace-template` option:
|
||||
|
||||
~~~
|
||||
qvm-backup-restore <backup_dir> --replace-template=fedora-15-x64:fedora-17-x64
|
||||
~~~
|
||||
63
developer/releases/1_0/release-notes.rst
Normal file
63
developer/releases/1_0/release-notes.rst
Normal file
|
|
@ -0,0 +1,63 @@
|
|||
========================
|
||||
Qubes R1.0 release notes
|
||||
========================
|
||||
|
||||
|
||||
Detailed release notes in `this blog post <https://blog.invisiblethings.org/2012/09/03/introducing-qubes-10.html>`__.
|
||||
|
||||
Known issues
|
||||
------------
|
||||
|
||||
|
||||
- Installer might not support some USB keyboards (#230). This seems to include all the Mac Book keyboards (most PC laptops have PS2 keyboards and are not affected).
|
||||
|
||||
- If you don’t enable Composition (System Setting -> Desktop -> Enable desktop effects), which you really should do, then the KDE task bar might get ugly (e.g. half of it might be black). This is some KDE bug that we don’t plan to fix.
|
||||
|
||||
- Some keyboard layout set by KDE System Settings can cause `keyboard not working at all <https://groups.google.com/group/qubes-devel/browse_thread/thread/77d076b65dda7226>`__. If you hit this issue, you can switch to console (by console login option) and manually edit ``/etc/X11/xorg.conf.d/00-system-setup-keyboard.conf`` (and ``/etc/sysconfig/keyboard``) and place correct keyboard layout settings (details in linked thread). You can check if specific keyboard layout settings are proper using ``setxkbmap`` tool.
|
||||
|
||||
- On systems with more than 8GB of RAM there is problem with DisposableVM. To fix it, limit maximum memory allocation for DispVM to 3GB
|
||||
|
||||
.. code:: bash
|
||||
|
||||
qvm-prefs -s fedora-17-x64-dvm maxmem 3072
|
||||
qvm-create-default-dvm --default-template --default-script
|
||||
|
||||
|
||||
|
||||
- On some systems the KDE Window Manager might freeze upon resuming from S3 sleep when compositing is enabled (and the only method to log in to the system if this happens is to switch to a text console, enter your user’s password, kill the kwin process, go back to the Xorg console, log in, and start a new instance of kwin using Konsole application :) If you experience such problems, make sure to disable compositing before putting the system into sleep by pressing Alt-Ctrl-F12 (and then enabling it back once you log in after resume) – this way you should never see this problem again.
|
||||
|
||||
|
||||
|
||||
Downloads
|
||||
---------
|
||||
|
||||
|
||||
See `Qubes Downloads <https://www.qubes-os.org/downloads/>`__.
|
||||
|
||||
Installation instructions
|
||||
-------------------------
|
||||
|
||||
|
||||
See :doc:`Installation Guide </user/downloading-installing-upgrading/installation-guide>`.
|
||||
|
||||
Upgrading
|
||||
---------
|
||||
|
||||
|
||||
From Qubes 1.0-rc1
|
||||
^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
If you’re already running Qubes 1.0-rc1, you don’t need to reinstall, it’s just enough to update the packages in your Dom0 and the template VM(s). The easiest way for doing this is to click on the Update Button in the Qubes Manger – one click when you selected Dom0, and one click for each of your template VM (by default there is just one template).
|
||||
|
||||
From Qubes 1.0 Beta 3
|
||||
^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
If you have Qubes Beta 3 currently installed on your system, you must reinstall from scratch, as we offer no direct upgrade option in the installer (sorry). However, we do offer tools for smooth migration of your AppVMs. In order to do that, please backup your AppVMs using the ``qvm-backup`` tool :doc:`as usual </user/how-to-guides/how-to-back-up-restore-and-migrate>`. Then, after you install Qubes 1.0 rc1, you can restore them using ``qvm-backup-restore`` tool. However, because we have changed the default template in RC1, you should tell qvm-back-restore about that by passing ``--replace-template`` option:
|
||||
|
||||
.. code:: bash
|
||||
|
||||
qvm-backup-restore <backup_dir> --replace-template=fedora-15-x64:fedora-17-x64
|
||||
|
||||
|
||||
|
|
@ -1,85 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/2.0/release-notes/
|
||||
redirect_from:
|
||||
- /en/doc/releases/2.0/release-notes/
|
||||
ref: 25
|
||||
title: Qubes R2.0 release notes
|
||||
---
|
||||
|
||||
Detailed release notes in [this blog post](https://blog.invisiblethings.org/2014/09/26/announcing-qubes-os-release-2.html)
|
||||
|
||||
## New features since 1.0
|
||||
|
||||
* Support for generic fully virtualized VMs (without qemu in the TCB!)
|
||||
* Support for Windows-based AppVMs integration (clipboard, file exchange, qrexec, pv drivers)
|
||||
* Secure audio input to select AppVMs (Hello Skype users!)
|
||||
* Clipboard is now also controlled by central policies, unified with other qrexec policies.
|
||||
* Out of the box TorVM support
|
||||
* Experimental support for PVUSB
|
||||
* Updated Xorg packages in Dom0 to support new GPUs
|
||||
* DisposableVM customization support
|
||||
* Introduced Xfce 4.10 environment for Dom0 as an alternative to KDE
|
||||
* Advanced infrastructure for system backups
|
||||
* Ability to autostart selected VM at system startup
|
||||
* Support for dynamic screen resolution change
|
||||
* Dom0 distribution upgraded to Fedora 20
|
||||
|
||||
## Known issues
|
||||
|
||||
* On some graphics cards the Xfce4 Window Manager (one of the two supported Dom0 Windows Managers in Qubes R2, the other being KDE) might behave "strangely", e.g. decorations might not be drawn sometimes. Also the accompanying lightdm login manager might incorrectly display the wallpaper. If you're facing those problems, it's advisable to use the KDE Window Manager and kdm instead of Xfce4 and lightdm (this is default if one chooses the KDE only installation option in the installer).
|
||||
|
||||
* Some icons in the Qubes Manager application might not be drawn correctly when using the Xfce4 environment in Dom0. If this bothers you, please use the KDE environment instead.
|
||||
|
||||
* If your GPU is not correctly supported by the Dom0 kernel (e.g. the 3D desktop effects do not run smoothly) then you might experience "heaviness" with Windows 7-based AppVMs. In that case, please solve the problem with your GPU support in Dom0 in the first place (by using a different kernel), or install Qubes OS on a different system.
|
||||
|
||||
* Under some circumstances, Qubes backup can create broken backup, without any visible message (\#902). It is advisable to verify a backup to spot the problem. If you encounter this problem, backup VM directory manually.
|
||||
|
||||
* System shutdown sometimes is very slow (\#903). To mitigate the problem, shutdown all the VMs first.
|
||||
|
||||
* For other known issues take a look at [our trac tickets](https://wiki.qubes-os.org/query?status=accepted&status=assigned&status=new&status=reopened&type=defect&milestone=Release+2.1+(post+R2)&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority)
|
||||
|
||||
It is advised to install updates just after system installation to apply bug fixes for (some of) the above problems.
|
||||
|
||||
## Downloads
|
||||
|
||||
See [Qubes Downloads](/doc/QubesDownloads/).
|
||||
|
||||
## Installation instructions
|
||||
|
||||
See [Installation Guide](/doc/installation-guide/).
|
||||
|
||||
## Upgrading
|
||||
|
||||
### From Qubes R2 rc1
|
||||
|
||||
Upgrading from Qubes R2 rc1 should be a simple matter of installing updates for [dom0](/doc/how-to-install-software-in-dom0/) and [VMs](/doc/software-update-vm/).
|
||||
|
||||
### From Qubes R2 beta 3 and older
|
||||
|
||||
The easiest and safest way to upgrade to Qubes R2 (especially from older releases) is to install it from scratch and use [qubes backup and restore tools](/doc/backup-restore/) for migrating of all of the user VMs.
|
||||
|
||||
Users of R2 beta 3 can upgrade using procedure that has been described [here](/doc/upgrade-to-r2/).
|
||||
|
||||
Note: if the user has custom Template VMs (i.e. other than the default template, e.g. created from it by cloning), or Standalone VMs, then the user should perform manual upgrade from R2B3 to R2rc1, as described under the link given above.
|
||||
|
||||
### Migrating between beta releases
|
||||
|
||||
#### From Qubes R1 to R2 beta1
|
||||
|
||||
If you're already running Qubes Release 1, you don't need to reinstall, it's just enough to update the packages in your Dom0 and the template VM(s). This procedure is described [here](/doc/upgrade-to-r2/).
|
||||
|
||||
#### From Qubes R1 or R2 Beta 1 to R2 beta2
|
||||
|
||||
Because of the distribution change in R2B2 (from fc13 to fc18) it's preferred that users reinstall Qubes R2B2 from scratch, and use [qubes backup and restore tools](/doc/backup-restore/) for migrating of all of the user VMs.
|
||||
|
||||
Advanced users (and advanced users only) can also try a manual upgrade procedure that has been described [here](/doc/upgrade-to-r2b2/). It's advisable to backup your VMs before proceeding anyway!
|
||||
|
||||
#### Upgrading from Qubes R1 or R2 Beta 2 to R2 beta 3
|
||||
|
||||
The easiest and safest way to upgrade to Qubes R2B3 is to install it from scratch and use [qubes backup and restore tools](/doc/backup-restore/) for migrating of all of the user VMs.
|
||||
|
||||
Users can also try a manual upgrade procedure that has been described [here](/doc/upgrade-to-r2b3/).
|
||||
|
||||
Note: if the user has custom Template VMs (i.e. other than the default template, e.g. created from it by cloning), or Standalone VMs, then the user should perform manual upgrade from R2B2 to R2B3, as described under the link given above.
|
||||
118
developer/releases/2_0/release-notes.rst
Normal file
118
developer/releases/2_0/release-notes.rst
Normal file
|
|
@ -0,0 +1,118 @@
|
|||
========================
|
||||
Qubes R2.0 release notes
|
||||
========================
|
||||
|
||||
|
||||
Detailed release notes in `this blog post <https://blog.invisiblethings.org/2014/09/26/announcing-qubes-os-release-2.html>`__
|
||||
|
||||
New features since 1.0
|
||||
----------------------
|
||||
|
||||
|
||||
- Support for generic fully virtualized VMs (without qemu in the TCB!)
|
||||
|
||||
- Support for Windows-based AppVMs integration (clipboard, file exchange, qrexec, pv drivers)
|
||||
|
||||
- Secure audio input to select AppVMs (Hello Skype users!)
|
||||
|
||||
- Clipboard is now also controlled by central policies, unified with other qrexec policies.
|
||||
|
||||
- Out of the box TorVM support
|
||||
|
||||
- Experimental support for PVUSB
|
||||
|
||||
- Updated Xorg packages in Dom0 to support new GPUs
|
||||
|
||||
- DisposableVM customization support
|
||||
|
||||
- Introduced Xfce 4.10 environment for Dom0 as an alternative to KDE
|
||||
|
||||
- Advanced infrastructure for system backups
|
||||
|
||||
- Ability to autostart selected VM at system startup
|
||||
|
||||
- Support for dynamic screen resolution change
|
||||
|
||||
- Dom0 distribution upgraded to Fedora 20
|
||||
|
||||
|
||||
|
||||
Known issues
|
||||
------------
|
||||
|
||||
|
||||
- On some graphics cards the Xfce4 Window Manager (one of the two supported Dom0 Windows Managers in Qubes R2, the other being KDE) might behave “strangely”, e.g. decorations might not be drawn sometimes. Also the accompanying lightdm login manager might incorrectly display the wallpaper. If you’re facing those problems, it’s advisable to use the KDE Window Manager and kdm instead of Xfce4 and lightdm (this is default if one chooses the KDE only installation option in the installer).
|
||||
|
||||
- Some icons in the Qubes Manager application might not be drawn correctly when using the Xfce4 environment in Dom0. If this bothers you, please use the KDE environment instead.
|
||||
|
||||
- If your GPU is not correctly supported by the Dom0 kernel (e.g. the 3D desktop effects do not run smoothly) then you might experience “heaviness” with Windows 7-based AppVMs. In that case, please solve the problem with your GPU support in Dom0 in the first place (by using a different kernel), or install Qubes OS on a different system.
|
||||
|
||||
- Under some circumstances, Qubes backup can create broken backup, without any visible message (#902). It is advisable to verify a backup to spot the problem. If you encounter this problem, backup VM directory manually.
|
||||
|
||||
- System shutdown sometimes is very slow (#903). To mitigate the problem, shutdown all the VMs first.
|
||||
|
||||
- For other known issues take a look at `our trac tickets <https://wiki.qubes-os.org/query?status=accepted&status=assigned&status=new&status=reopened&type=defect&milestone=Release+2.1+(post+R2)&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority>`__
|
||||
|
||||
|
||||
|
||||
It is advised to install updates just after system installation to apply bug fixes for (some of) the above problems.
|
||||
|
||||
Downloads
|
||||
---------
|
||||
|
||||
|
||||
See `Qubes Downloads <https://www.qubes-os.org/downloads/>`__.
|
||||
|
||||
Installation instructions
|
||||
-------------------------
|
||||
|
||||
|
||||
See :doc:`Installation Guide </user/downloading-installing-upgrading/installation-guide>`.
|
||||
|
||||
Upgrading
|
||||
---------
|
||||
|
||||
|
||||
From Qubes R2 rc1
|
||||
^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
Upgrading from Qubes R2 rc1 should be a simple matter of installing updates for :doc:`dom0 </user/advanced-topics/how-to-install-software-in-dom0>` and :doc:`VMs </user/how-to-guides/how-to-install-software>`.
|
||||
|
||||
From Qubes R2 beta 3 and older
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
The easiest and safest way to upgrade to Qubes R2 (especially from older releases) is to install it from scratch and use :doc:`qubes backup and restore tools </user/how-to-guides/how-to-back-up-restore-and-migrate>` for migrating of all of the user VMs.
|
||||
|
||||
Users of R2 beta 3 can upgrade using procedure that has been described :doc:`here </user/downloading-installing-upgrading/upgrade/2>`.
|
||||
|
||||
**Note:** if the user has custom Template VMs (i.e. other than the default template, e.g. created from it by cloning), or Standalone VMs, then the user should perform manual upgrade from R2B3 to R2rc1, as described under the link given above.
|
||||
|
||||
Migrating between beta releases
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
From Qubes R1 to R2 beta1
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
If you’re already running Qubes Release 1, you don’t need to reinstall, it’s just enough to update the packages in your Dom0 and the template VM(s). This procedure is described :doc:`here </user/downloading-installing-upgrading/upgrade/2>`.
|
||||
|
||||
From Qubes R1 or R2 Beta 1 to R2 beta2
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
Because of the distribution change in R2B2 (from fc13 to fc18) it’s preferred that users reinstall Qubes R2B2 from scratch, and use :doc:`qubes backup and restore tools </user/how-to-guides/how-to-back-up-restore-and-migrate>` for migrating of all of the user VMs.
|
||||
|
||||
Advanced users (and advanced users only) can also try a manual upgrade procedure that has been described :doc:`here </user/downloading-installing-upgrading/upgrade/2b2>`. It’s advisable to backup your VMs before proceeding anyway!
|
||||
|
||||
Upgrading from Qubes R1 or R2 Beta 2 to R2 beta 3
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
The easiest and safest way to upgrade to Qubes R2B3 is to install it from scratch and use :doc:`qubes backup and restore tools </user/how-to-guides/how-to-back-up-restore-and-migrate>` for migrating of all of the user VMs.
|
||||
|
||||
Users can also try a manual upgrade procedure that has been described :doc:`here </user/downloading-installing-upgrading/upgrade/2b3>`.
|
||||
|
||||
**Note:** if the user has custom Template VMs (i.e. other than the default template, e.g. created from it by cloning), or Standalone VMs, then the user should perform manual upgrade from R2B2 to R2B3, as described under the link given above.
|
||||
|
|
@ -1,62 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/3.0/release-notes/
|
||||
redirect_from:
|
||||
- /en/doc/releases/3.0/release-notes/
|
||||
ref: 19
|
||||
title: Qubes R3.0 release notes
|
||||
---
|
||||
|
||||
### Qubes R3.0 Release Notes
|
||||
|
||||
This Qubes OS release is dedicated to the memory of Caspar Bowden.
|
||||
|
||||
## New features since 2.0
|
||||
|
||||
* HAL (Hypervisor Abstraction Layer) - based on libvirt, opens a whole new
|
||||
possibilities of using different hypervisors. Currently Qubes OS uses Xen.
|
||||
* Xen 4.4 - many new features, but for us the most important is much more
|
||||
mature libxl toolstack.
|
||||
* Qrexec 3 - greatly improved performance by using direct VM-VM connections and
|
||||
bigger buffers.
|
||||
* Debian templates gets official support.
|
||||
* Whonix templates
|
||||
* Build system improvements - especially support for distribution-specific
|
||||
plugins (makes supporting multiple distributions much easier) and building
|
||||
templates using DispVM.
|
||||
* Automated tests - makes much easier to find bugs, before its even shipped to users
|
||||
|
||||
## Known issues
|
||||
|
||||
* Windows Tools: `qvm-block` does not work
|
||||
|
||||
* UEFI is not supported, you need to enable "legacy boot" in BIOS before installing Qubes OS
|
||||
|
||||
* Some icons in the Qubes Manager application might not be drawn correctly when using the Xfce4 environment in Dom0. If this bothers you, please use the KDE environment instead.
|
||||
|
||||
* If your GPU is not correctly supported by the Dom0 kernel (e.g. the 3D desktop effects do not run smoothly) then you might experience "heaviness" with Windows 7-based AppVMs. In that case, please solve the problem with your GPU support in Dom0 in the first place (by using a different kernel), or install Qubes OS on a different system.
|
||||
|
||||
* For other known issues take a look at [our tickets](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+3.0%22+label%3Abug)
|
||||
|
||||
It is advised to install updates just after system installation to apply bug fixes for (some of) the above problems.
|
||||
|
||||
## Downloads
|
||||
|
||||
See [Qubes Downloads](/doc/QubesDownloads/).
|
||||
|
||||
## Installation instructions
|
||||
|
||||
See [Installation Guide](/doc/installation-guide/).
|
||||
|
||||
## Upgrading
|
||||
|
||||
### From R3.0 release candidate
|
||||
|
||||
If you are using Qubes R3.0rc1, R3.0rc2 or R3.0rc3, just install system updates, there is no special steps required.
|
||||
|
||||
### From R2.0 or earlier
|
||||
|
||||
The easiest and safest way to upgrade to Qubes R3.0 is to install it from scratch and use [qubes backup and restore tools](/doc/backup-restore/) for migrating of all of the user VMs.
|
||||
|
||||
Users of Qubes R2 can upgrade using [experimental procedure](/doc/upgrade-to-r3.0/).
|
||||
80
developer/releases/3_0/release-notes.rst
Normal file
80
developer/releases/3_0/release-notes.rst
Normal file
|
|
@ -0,0 +1,80 @@
|
|||
========================
|
||||
Qubes R3.0 release notes
|
||||
========================
|
||||
|
||||
|
||||
Qubes R3.0 Release Notes
|
||||
------------------------
|
||||
|
||||
|
||||
|
||||
|
||||
This Qubes OS release is dedicated to the memory of Caspar Bowden.
|
||||
|
||||
New features since 2.0
|
||||
^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
- HAL (Hypervisor Abstraction Layer) - based on libvirt, opens a whole new possibilities of using different hypervisors. Currently Qubes OS uses Xen.
|
||||
|
||||
- Xen 4.4 - many new features, but for us the most important is much more mature libxl toolstack.
|
||||
|
||||
- Qrexec 3 - greatly improved performance by using direct VM-VM connections and bigger buffers.
|
||||
|
||||
- Debian templates gets official support.
|
||||
|
||||
- Whonix templates
|
||||
|
||||
- Build system improvements - especially support for distribution-specific plugins (makes supporting multiple distributions much easier) and building templates using DispVM.
|
||||
|
||||
- Automated tests - makes much easier to find bugs, before its even shipped to users
|
||||
|
||||
|
||||
|
||||
Known issues
|
||||
^^^^^^^^^^^^
|
||||
|
||||
|
||||
- Windows Tools: ``qvm-block`` does not work
|
||||
|
||||
- UEFI is not supported, you need to enable “legacy boot” in BIOS before installing Qubes OS
|
||||
|
||||
- Some icons in the Qubes Manager application might not be drawn correctly when using the Xfce4 environment in Dom0. If this bothers you, please use the KDE environment instead.
|
||||
|
||||
- If your GPU is not correctly supported by the Dom0 kernel (e.g. the 3D desktop effects do not run smoothly) then you might experience “heaviness” with Windows 7-based AppVMs. In that case, please solve the problem with your GPU support in Dom0 in the first place (by using a different kernel), or install Qubes OS on a different system.
|
||||
|
||||
- For other known issues take a look at `our tickets <https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+3.0%22+label%3Abug>`__
|
||||
|
||||
|
||||
|
||||
It is advised to install updates just after system installation to apply bug fixes for (some of) the above problems.
|
||||
|
||||
Downloads
|
||||
^^^^^^^^^
|
||||
|
||||
|
||||
See `Qubes Downloads <https://www.qubes-os.org/downloads/>`__.
|
||||
|
||||
Installation instructions
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
See :doc:`Installation Guide </user/downloading-installing-upgrading/installation-guide>`.
|
||||
|
||||
Upgrading
|
||||
^^^^^^^^^
|
||||
|
||||
|
||||
From R3.0 release candidate
|
||||
---------------------------
|
||||
|
||||
|
||||
If you are using Qubes R3.0rc1, R3.0rc2 or R3.0rc3, just install system updates, there is no special steps required.
|
||||
|
||||
From R2.0 or earlier
|
||||
--------------------
|
||||
|
||||
|
||||
The easiest and safest way to upgrade to Qubes R3.0 is to install it from scratch and use :doc:`qubes backup and restore tools </user/how-to-guides/how-to-back-up-restore-and-migrate>` for migrating of all of the user VMs.
|
||||
|
||||
Users of Qubes R2 can upgrade using :doc:`experimental procedure </user/downloading-installing-upgrading/upgrade/3_0>`.
|
||||
|
|
@ -1,15 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/3.0/schedule/
|
||||
redirect_from:
|
||||
- /en/doc/releases/3.0/schedule/
|
||||
ref: 20
|
||||
title: Qubes R3.0 release schedule
|
||||
---
|
||||
|
||||
| Date | Stage |
|
||||
| -----------:| ------------------------------------- |
|
||||
| 5 Sep 2015 | current-testing freeze before 3.0-rc3 |
|
||||
| 15 Sep 2015 | 3.0-rc3 release |
|
||||
| 1 Oct 2015 | 3.0 release |
|
||||
20
developer/releases/3_0/schedule.rst
Normal file
20
developer/releases/3_0/schedule.rst
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
===========================
|
||||
Qubes R3.0 release schedule
|
||||
===========================
|
||||
|
||||
|
||||
.. list-table::
|
||||
:widths: 11 11
|
||||
:align: center
|
||||
:header-rows: 1
|
||||
|
||||
* - Date
|
||||
- Stage
|
||||
* - 5 Sep 2015
|
||||
- current-testing freeze before 3.0-rc3
|
||||
* - 15 Sep 2015
|
||||
- 3.0-rc3 release
|
||||
* - 1 Oct 2015
|
||||
- 3.0 release
|
||||
|
||||
|
||||
|
|
@ -1,65 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/3.1/release-notes/
|
||||
ref: 16
|
||||
title: Qubes R3.1 release notes
|
||||
---
|
||||
|
||||
## New features since 3.0
|
||||
|
||||
* Management Stack based of Salt Stack in dom0 - [documentation](/doc/salt/)
|
||||
* Out of the box Whonix setup
|
||||
* UEFI support
|
||||
* LIVE edition (still alpha, not part of R3.1-rc1)
|
||||
* Updated GPU drivers in dom0
|
||||
* Colorful window application icons (instead of just colorful lock icon)
|
||||
* PV Grub support ([documentation](/doc/managing-vm-kernels/))
|
||||
* Out of the box USB VM setup, including [handling USB mouse](https://github.com/QubesOS/qubes-app-linux-input-proxy/blob/master/README.md)
|
||||
* Xen upgraded to 4.6, for better hardware support (especially Skylake platform)
|
||||
* Improve updates proxy flexibility - especially repositories served over HTTPS
|
||||
|
||||
You can get detailed description in [completed github issues](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+milestone%3A%22Release+3.1%22+label%3Arelease-notes+is%3Aclosed)
|
||||
|
||||
## Known issues
|
||||
|
||||
* Installation image does not fit on DVD, requires either DVD DL, or USB stick (5GB or more)
|
||||
|
||||
* Windows Tools: `qvm-block` does not work
|
||||
|
||||
* Some icons in the Qubes Manager application might not be drawn correctly when using the Xfce4 environment in Dom0. If this bothers you, please use the KDE environment instead.
|
||||
|
||||
* USB mouse (in the case of USB VM) does not work at first system startup (just after completing firstboot). Workaround: restart the system.
|
||||
|
||||
* For other known issues take a look at [our tickets](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+3.1%22+label%3Abug)
|
||||
|
||||
It is advised to install updates just after system installation to apply bug fixes for (some of) the above problems.
|
||||
|
||||
## Downloads
|
||||
|
||||
See [Qubes Downloads](/downloads/).
|
||||
|
||||
## Installation instructions
|
||||
|
||||
See [Installation Guide](/doc/installation-guide/).
|
||||
|
||||
## Upgrading
|
||||
|
||||
### From R3.0
|
||||
|
||||
The easiest and safest way to upgrade to Qubes R3.1 is to install it from
|
||||
scratch and use [qubes backup and restore tools](/doc/backup-restore/) for
|
||||
migrating of all of the user VMs.
|
||||
|
||||
Users of Qubes R3.0 can upgrade using [experimental
|
||||
procedure](/doc/upgrade-to-r3.1/).
|
||||
|
||||
### From R2 or earlier
|
||||
|
||||
When upgrading from earlier versions the easiest and safest way is to install
|
||||
it from scratch and use [qubes backup and restore tools](/doc/backup-restore/)
|
||||
for migrating of all of the user VMs.
|
||||
|
||||
Alternatively you can [upgrade to R3.0
|
||||
using](/doc/releases/3.0/release-notes/#upgrading) first, then follow the
|
||||
instructions above. This will be time consuming process.
|
||||
82
developer/releases/3_1/release-notes.rst
Normal file
82
developer/releases/3_1/release-notes.rst
Normal file
|
|
@ -0,0 +1,82 @@
|
|||
========================
|
||||
Qubes R3.1 release notes
|
||||
========================
|
||||
|
||||
|
||||
New features since 3.0
|
||||
----------------------
|
||||
|
||||
|
||||
- Management Stack based of Salt Stack in dom0 - :doc:`documentation </user/advanced-topics/salt>`
|
||||
|
||||
- Out of the box Whonix setup
|
||||
|
||||
- UEFI support
|
||||
|
||||
- LIVE edition (still alpha, not part of R3.1-rc1)
|
||||
|
||||
- Updated GPU drivers in dom0
|
||||
|
||||
- Colorful window application icons (instead of just colorful lock icon)
|
||||
|
||||
- PV Grub support (:doc:`documentation </user/advanced-topics/managing-vm-kernels>`)
|
||||
|
||||
- Out of the box USB VM setup, including `handling USB mouse <https://github.com/QubesOS/qubes-app-linux-input-proxy/blob/master/README.md>`__
|
||||
|
||||
- Xen upgraded to 4.6, for better hardware support (especially Skylake platform)
|
||||
|
||||
- Improve updates proxy flexibility - especially repositories served over HTTPS
|
||||
|
||||
|
||||
|
||||
You can get detailed description in `completed github issues <https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+milestone%3A%22Release+3.1%22+label%3Arelease-notes+is%3Aclosed>`__
|
||||
|
||||
Known issues
|
||||
------------
|
||||
|
||||
|
||||
- Installation image does not fit on DVD, requires either DVD DL, or USB stick (5GB or more)
|
||||
|
||||
- Windows Tools: ``qvm-block`` does not work
|
||||
|
||||
- Some icons in the Qubes Manager application might not be drawn correctly when using the Xfce4 environment in Dom0. If this bothers you, please use the KDE environment instead.
|
||||
|
||||
- USB mouse (in the case of USB VM) does not work at first system startup (just after completing firstboot). Workaround: restart the system.
|
||||
|
||||
- For other known issues take a look at `our tickets <https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+3.1%22+label%3Abug>`__
|
||||
|
||||
|
||||
|
||||
It is advised to install updates just after system installation to apply bug fixes for (some of) the above problems.
|
||||
|
||||
Downloads
|
||||
---------
|
||||
|
||||
|
||||
See `Qubes Downloads <https://www.qubes-os.org/downloads/>`__.
|
||||
|
||||
Installation instructions
|
||||
-------------------------
|
||||
|
||||
|
||||
See :doc:`Installation Guide </user/downloading-installing-upgrading/installation-guide>`.
|
||||
|
||||
Upgrading
|
||||
---------
|
||||
|
||||
|
||||
From R3.0
|
||||
^^^^^^^^^
|
||||
|
||||
|
||||
The easiest and safest way to upgrade to Qubes R3.1 is to install it from scratch and use :doc:`qubes backup and restore tools </user/how-to-guides/how-to-back-up-restore-and-migrate>` for migrating of all of the user VMs.
|
||||
|
||||
Users of Qubes R3.0 can upgrade using :doc:`experimental procedure </user/downloading-installing-upgrading/upgrade/3_1>`.
|
||||
|
||||
From R2 or earlier
|
||||
^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
When upgrading from earlier versions the easiest and safest way is to install it from scratch and use :doc:`qubes backup and restore tools </user/how-to-guides/how-to-back-up-restore-and-migrate>` for migrating of all of the user VMs.
|
||||
|
||||
Alternatively you can :ref:`upgrade to R3.0 using <developer/releases/3_0/release-notes:upgrading>` first, then follow the instructions above. This will be time consuming process.
|
||||
|
|
@ -1,20 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/3.1/schedule/
|
||||
redirect_from:
|
||||
- /en/doc/releases/3.1/schedule/
|
||||
ref: 17
|
||||
title: Qubes R3.1 release schedule
|
||||
---
|
||||
|
||||
This schedule is based on [Version Scheme](/doc/version-scheme/#release-schedule).
|
||||
|
||||
| Date | Stage |
|
||||
| -----------:| --------------------------------------- |
|
||||
| 8 Dec 2015 | 3.1-rc1 release |
|
||||
| 5 Jan 2016 | current-testing freeze before 3.1-rc2 |
|
||||
| 12 Jan 2016 | 3.1-rc2 release |
|
||||
| 26 Jan 2016 | decide whether 3.1-rc2 is the final 3.1 |
|
||||
| 9 Feb 2016 | current-testing freeze before 3.1-rc3 |
|
||||
| ~~16 Feb 2016~~ <br/> 23 Feb 2016 | 3.1-rc3 release |
|
||||
28
developer/releases/3_1/schedule.rst
Normal file
28
developer/releases/3_1/schedule.rst
Normal file
|
|
@ -0,0 +1,28 @@
|
|||
===========================
|
||||
Qubes R3.1 release schedule
|
||||
===========================
|
||||
|
||||
|
||||
This schedule is based on :ref:`Version Scheme <developer/releases/version-scheme:release schedule>`.
|
||||
|
||||
.. list-table::
|
||||
:widths: 38 38
|
||||
:align: center
|
||||
:header-rows: 1
|
||||
|
||||
* - Date
|
||||
- Stage
|
||||
* - 8 Dec 2015
|
||||
- 3.1-rc1 release
|
||||
* - 5 Jan 2016
|
||||
- current-testing freeze before 3.1-rc2
|
||||
* - 12 Jan 2016
|
||||
- 3.1-rc2 release
|
||||
* - 26 Jan 2016
|
||||
- decide whether 3.1-rc2 is the final 3.1
|
||||
* - 9 Feb 2016
|
||||
- current-testing freeze before 3.1-rc3
|
||||
* - :strike:`16 Feb 2016` 23 Feb 2016
|
||||
- 3.1-rc3 release
|
||||
|
||||
|
||||
|
|
@ -1,61 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/3.2/release-notes/
|
||||
ref: 21
|
||||
title: Qubes R3.2 release notes
|
||||
---
|
||||
|
||||
## New features since 3.1
|
||||
|
||||
* Management Stack extended to support in-VM configuration - [documentation](/doc/salt/)
|
||||
* PV USB - [documentation](/doc/usb/)
|
||||
* Dom0 update to Fedora 23 for better hardware support
|
||||
* Kernel 4.4.x
|
||||
* Default desktop environment switched to Xfce4
|
||||
* KDE 5 support (but it is no longer the default one)
|
||||
* Tiling window managers support: awesome, [i3](/doc/i3/)
|
||||
* More flexible Qubes RPC services - [related ticket](https://github.com/QubesOS/qubes-issues/issues/1876), [documentation](/doc/qrexec/#service-policies-with-arguments)
|
||||
|
||||
You can get detailed description in [completed github issues](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+milestone%3A%22Release+3.2%22+label%3Arelease-notes+is%3Aclosed)
|
||||
|
||||
## Known issues
|
||||
|
||||
* [Fedora 23 reached EOL in December 2016](https://fedoraproject.org/wiki/End_of_life). There is a [manual procedure to upgrade your VMs](/news/2018/01/06/fedora-26-upgrade/).
|
||||
|
||||
* Windows Tools: `qvm-block` does not work
|
||||
|
||||
* Some icons in the Qubes Manager application might not be drawn correctly when using the Xfce4 environment in Dom0. If this bothers you, please use the KDE environment instead.
|
||||
|
||||
* For other known issues take a look at [our tickets](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+3.2%22+label%3Abug)
|
||||
|
||||
It is advised to install updates just after system installation to apply bug fixes for (some of) the above problems.
|
||||
|
||||
## Downloads
|
||||
|
||||
See [Qubes Downloads](/downloads/).
|
||||
|
||||
## Installation instructions
|
||||
|
||||
See [Installation Guide](/doc/installation-guide/).
|
||||
After installation, [manually upgrade to Fedora 26](/news/2018/01/06/fedora-26-upgrade/).
|
||||
|
||||
## Upgrading
|
||||
|
||||
### From R3.1
|
||||
|
||||
The easiest and safest way to upgrade to Qubes R3.2 is to install it from
|
||||
scratch and use [qubes backup and restore tools](/doc/backup-restore/) for
|
||||
migrating of all of the user VMs.
|
||||
|
||||
Users of Qubes R3.1 can also upgrade using [this
|
||||
procedure](/doc/upgrade-to-r3.2/).
|
||||
|
||||
### From R3.0 or earlier
|
||||
|
||||
When upgrading from earlier versions the easiest and safest way is to install
|
||||
it from scratch and use [qubes backup and restore tools](/doc/backup-restore/)
|
||||
for migrating of all of the user VMs.
|
||||
|
||||
Alternatively you can [upgrade to R3.1 using](/doc/releases/3.1/release-notes/#upgrading) first, then follow
|
||||
the instructions above. This will be time consuming process.
|
||||
76
developer/releases/3_2/release-notes.rst
Normal file
76
developer/releases/3_2/release-notes.rst
Normal file
|
|
@ -0,0 +1,76 @@
|
|||
========================
|
||||
Qubes R3.2 release notes
|
||||
========================
|
||||
|
||||
|
||||
New features since 3.1
|
||||
----------------------
|
||||
|
||||
|
||||
- Management Stack extended to support in-VM configuration - :doc:`documentation </user/advanced-topics/salt>`
|
||||
|
||||
- PV USB - :doc:`documentation </user/how-to-guides/how-to-use-usb-devices>`
|
||||
|
||||
- Dom0 update to Fedora 23 for better hardware support
|
||||
|
||||
- Kernel 4.4.x
|
||||
|
||||
- Default desktop environment switched to Xfce4
|
||||
|
||||
- KDE 5 support (but it is no longer the default one)
|
||||
|
||||
- Tiling window managers support: awesome, :doc:`i3 </user/advanced-topics/i3>`
|
||||
|
||||
- More flexible Qubes RPC services - `related ticket <https://github.com/QubesOS/qubes-issues/issues/1876>`__, :ref:`documentation <developer/services/qrexec:service policies with arguments>`
|
||||
|
||||
|
||||
|
||||
You can get detailed description in `completed github issues <https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+milestone%3A%22Release+3.2%22+label%3Arelease-notes+is%3Aclosed>`__
|
||||
|
||||
Known issues
|
||||
------------
|
||||
|
||||
|
||||
- `Fedora 23 reached EOL in December 2016 <https://fedoraproject.org/wiki/End_of_life>`__. There is a `manual procedure to upgrade your VMs <https://www.qubes-os.org/news/2018/01/06/fedora-26-upgrade/>`__.
|
||||
|
||||
- Windows Tools: ``qvm-block`` does not work
|
||||
|
||||
- Some icons in the Qubes Manager application might not be drawn correctly when using the Xfce4 environment in Dom0. If this bothers you, please use the KDE environment instead.
|
||||
|
||||
- For other known issues take a look at `our tickets <https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+3.2%22+label%3Abug>`__
|
||||
|
||||
|
||||
|
||||
It is advised to install updates just after system installation to apply bug fixes for (some of) the above problems.
|
||||
|
||||
Downloads
|
||||
---------
|
||||
|
||||
|
||||
See `Qubes Downloads <https://www.qubes-os.org/downloads/>`__.
|
||||
|
||||
Installation instructions
|
||||
-------------------------
|
||||
|
||||
|
||||
See :doc:`Installation Guide </user/downloading-installing-upgrading/installation-guide>`. After installation, `manually upgrade to Fedora 26 <https://www.qubes-os.org/news/2018/01/06/fedora-26-upgrade/>`__.
|
||||
|
||||
Upgrading
|
||||
---------
|
||||
|
||||
|
||||
From R3.1
|
||||
^^^^^^^^^
|
||||
|
||||
|
||||
The easiest and safest way to upgrade to Qubes R3.2 is to install it from scratch and use :doc:`qubes backup and restore tools </user/how-to-guides/how-to-back-up-restore-and-migrate>` for migrating of all of the user VMs.
|
||||
|
||||
Users of Qubes R3.1 can also upgrade using :doc:`this procedure </user/downloading-installing-upgrading/upgrade/3_2>`.
|
||||
|
||||
From R3.0 or earlier
|
||||
^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
When upgrading from earlier versions the easiest and safest way is to install it from scratch and use :doc:`qubes backup and restore tools </user/how-to-guides/how-to-back-up-restore-and-migrate>` for migrating of all of the user VMs.
|
||||
|
||||
Alternatively you can :ref:`upgrade to R3.1 using <developer/releases/3_1/release-notes:upgrading>` first, then follow the instructions above. This will be time consuming process.
|
||||
|
|
@ -1,22 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/3.2/schedule/
|
||||
redirect_from:
|
||||
- /en/doc/releases/3.2/schedule/
|
||||
ref: 22
|
||||
title: Qubes R3.2 release schedule
|
||||
---
|
||||
|
||||
This schedule is based on [Version Scheme](/doc/version-scheme/#release-schedule).
|
||||
|
||||
| Date | Stage |
|
||||
| -----------:| --------------------------------------- |
|
||||
| 18 Jun 2016 | 3.2-rc1 release |
|
||||
| 2 Jul 2016 | decide whether 3.2-rc1 is the final 3.2 |
|
||||
| ~~16 Jul 2016~~ <br/> 20 Jul 2016 | current-testing freeze before 3.2-rc2 |
|
||||
| ~~23 Jul 2016~~ <br/> 27 Jul 2016 | 3.2-rc2 release |
|
||||
| ~~5 Aug 2016~~ <br/> 9 Aug 2016 | decide whether 3.2-rc2 is the final 3.2 |
|
||||
| 24 Aug 2016 | current-testing freeze before 3.2-rc3 |
|
||||
| 31 Aug 2016 | 3.2-rc3 release |
|
||||
| 29 Sep 2016 | 3.2 release |
|
||||
32
developer/releases/3_2/schedule.rst
Normal file
32
developer/releases/3_2/schedule.rst
Normal file
|
|
@ -0,0 +1,32 @@
|
|||
===========================
|
||||
Qubes R3.2 release schedule
|
||||
===========================
|
||||
|
||||
|
||||
This schedule is based on :ref:`Version Scheme <developer/releases/version-scheme:release schedule>`.
|
||||
|
||||
.. list-table::
|
||||
:widths: 38 38
|
||||
:align: center
|
||||
:header-rows: 1
|
||||
|
||||
* - Date
|
||||
- Stage
|
||||
* - 18 Jun 2016
|
||||
- 3.2-rc1 release
|
||||
* - 2 Jul 2016
|
||||
- decide whether 3.2-rc1 is the final 3.2
|
||||
* - :strike:`16 Jul 2016` 20 Jul 2016
|
||||
- current-testing freeze before 3.2-rc2
|
||||
* - :strike:`23 Jul 2016` 27 Jul 2016
|
||||
- 3.2-rc2 release
|
||||
* - :strike:`5 Aug 2016` 9 Aug 2016
|
||||
- decide whether 3.2-rc2 is the final 3.2
|
||||
* - 24 Aug 2016
|
||||
- current-testing freeze before 3.2-rc3
|
||||
* - 31 Aug 2016
|
||||
- 3.2-rc3 release
|
||||
* - 29 Sep 2016
|
||||
- 3.2 release
|
||||
|
||||
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/4.0/release-notes/
|
||||
ref: 23
|
||||
title: Qubes R4.0 release notes
|
||||
---
|
||||
|
||||
New features since 3.2
|
||||
----------------------
|
||||
|
||||
* Core management scripts rewrite with better structure and extensibility, [current API documentation](https://dev.qubes-os.org/projects/core-admin/en/latest/) and the documentation API index as a [webarchive](https://web.archive.org/web/20230128102821/https://dev.qubes-os.org/projects/qubes-core-admin/en/latest/)
|
||||
* [Admin API](/news/2017/06/27/qubes-admin-api/) allowing strictly controlled managing from non-dom0
|
||||
* All `qvm-*` command-line tools rewritten, some options have changed
|
||||
* Renaming VM directly is prohibited, there is GUI to clone under new name and remove old VM
|
||||
* Use [PVH](https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-037-2018.txt) and [HVM](https://github.com/QubesOS/qubes-issues/issues/2185) by default to [mitigate Meltdown & Spectre](https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-037-2018.txt) and lower the [attack surface on Xen](https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-024-2016.txt)
|
||||
* Create USB VM by default
|
||||
* [Multiple DisposableVMs templates support](https://github.com/QubesOS/qubes-issues/issues/2253)
|
||||
* New [backup format](/doc/backup-emergency-restore-v4/) using scrypt key-derivation function
|
||||
* Non-encrypted backups no longer supported
|
||||
* [split VM packages](https://github.com/QubesOS/qubes-issues/issues/2771), for better support minimal, specialized templates
|
||||
* [Qubes Manager decomposition](https://github.com/QubesOS/qubes-issues/issues/2132) - domains and devices widgets instead of full Qubes Manager; devices widget support also USB
|
||||
* [More flexible firewall interface](/doc/vm-interface/) for ease unikernel integration
|
||||
* Template VMs do not have network interface by default, [qrexec-based updates proxy](https://github.com/QubesOS/qubes-issues/issues/1854) is used instead
|
||||
* More flexible IP addressing for VMs - [custom IP](https://github.com/QubesOS/qubes-issues/issues/1477), [hidden from the IP](https://github.com/QubesOS/qubes-issues/issues/1143)
|
||||
* More flexible Qubes RPC policy - [related ticket](https://github.com/QubesOS/qubes-issues/issues/865), [documentation](/doc/qrexec/#specifying-vms-tags-types-targets-etc)
|
||||
* [New Qubes RPC confirmation window](https://github.com/QubesOS/qubes-issues/issues/910), including option to specify destination VM
|
||||
* [New storage subsystem design](https://github.com/QubesOS/qubes-issues/issues/1842)
|
||||
* Dom0 update to Fedora 25 for better hardware support
|
||||
* Kernel 4.9.x
|
||||
|
||||
You can get detailed description in [completed github issues](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+milestone%3A%22Release+4.0%22+label%3Arelease-notes+is%3Aclosed)
|
||||
|
||||
Security Notes
|
||||
--------------
|
||||
|
||||
* PV VMs migrated from 3.2 to 4.0-rc4 or later are automatically set to PVH mode in order to protect against Meltdown (see [QSB #37](https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-037-2018.txt)).
|
||||
However, PV VMs migrated from any earlier 4.0 release candidate (RC1, RC2, or RC3) are not automatically set to PVH mode.
|
||||
These must be set manually.
|
||||
|
||||
* The following steps may need to be applied in dom0 and Fedora 26 TemplateVMs in order to receive updates (see [#3737](https://github.com/QubesOS/qubes-issues/issues/3737)).
|
||||
|
||||
Steps for dom0 updates:
|
||||
|
||||
1. Open the Qubes Menu by clicking on the "Q" icon in the top-left corner of the screen.
|
||||
2. Select `Terminal Emulator`.
|
||||
3. In the window that opens, enter this command:
|
||||
|
||||
```
|
||||
sudo nano /etc/yum.repos.d/qubes-dom0.repo
|
||||
```
|
||||
|
||||
4. This opens the nano text editor. Change all four instances of `http` to `https`.
|
||||
5. Press `CTRL+X`, then `Y`, then `ENTER` to save changes and exit.
|
||||
6. Check for updates normally.
|
||||
|
||||
Steps for Fedora 26 TemplateVM updates:
|
||||
|
||||
1. Open the Qubes Menu by clicking on the "Q" icon in the top-left corner of the screen.
|
||||
2. Select `Template: fedora-26`, then `fedora-26: Terminal`.
|
||||
3. In the window that opens, enter the command for your version:
|
||||
|
||||
```
|
||||
[Qubes 3.2] sudo gedit /etc/yum.repos.d/qubes-r3.repo
|
||||
[Qubes 4.0] sudo gedit /etc/yum.repos.d/qubes-r4.repo
|
||||
```
|
||||
|
||||
4. This opens the gedit text editor in a window. Change all four instances of `http` to `https`.
|
||||
5. Click the "Save" button in the top-right corner of the window.
|
||||
6. Close the window.
|
||||
7. Check for updates normally.
|
||||
8. Shut down the TemplateVM.
|
||||
|
||||
Known issues
|
||||
------------
|
||||
|
||||
* Locale using coma as decimal separator [crashes qubesd](https://github.com/QubesOS/qubes-issues/issues/3753). Either install with different locale (English (United States) for example), or manually apply fix explained in that issue.
|
||||
|
||||
* In the middle of installation, [keyboard layout reset to US](https://github.com/QubesOS/qubes-issues/issues/3352). Be careful what is the current layout while setting default user password (see upper right screen corner).
|
||||
|
||||
* On some laptops (for example Librem 15v2), touchpad do not work directly after installation. Reboot the system to fix the issue.
|
||||
|
||||
* List of USB devices may contain device identifiers instead of name
|
||||
|
||||
* With R4.0.1, which ships kernel-4.19, you may never reach the anaconda startup and be block on an idle black screen with blinking cursor. You can try to add `plymouth.ignore-serial-consoles` in the grub installer boot menu right after `quiet rhgb`. With legacy mode, you can do it directly when booting the DVD or USB key. In UEFI mode, follow the same procedure described for [disabling](/doc/uefi-troubleshooting/#installation-freezes-before-displaying-installer) `nouveau` module (related [solved issue](https://github.com/QubesOS/qubes-issues/issues/3849) in further version of Qubes).
|
||||
|
||||
* For other known issues take a look at [our tickets](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+4.0%22+label%3Abug)
|
||||
|
||||
It is advised to install updates just after system installation to apply bug fixes for (some of) the above problems.
|
||||
|
||||
Downloads
|
||||
---------
|
||||
|
||||
See [Qubes Downloads](/downloads/).
|
||||
|
||||
Installation instructions
|
||||
-------------------------
|
||||
|
||||
See [Installation Guide](/doc/installation-guide/).
|
||||
|
||||
Upgrading
|
||||
---------
|
||||
|
||||
There is no in-place upgrade path from earlier Qubes versions. The only
|
||||
supported option to upgrade to Qubes R4.0 is to install it from scratch and use
|
||||
[qubes backup and restore tools](/doc/backup-restore/) for migrating of all of the user VMs.
|
||||
We also provide [detailed instruction](/doc/upgrade-to-r4.0/) for this procedure.
|
||||
145
developer/releases/4_0/release-notes.rst
Normal file
145
developer/releases/4_0/release-notes.rst
Normal file
|
|
@ -0,0 +1,145 @@
|
|||
========================
|
||||
Qubes R4.0 release notes
|
||||
========================
|
||||
|
||||
|
||||
New features since 3.2
|
||||
----------------------
|
||||
|
||||
|
||||
- Core management scripts rewrite with better structure and extensibility, `current API documentation <https://dev.qubes-os.org/projects/core-admin/en/latest/>`__ and the documentation API index as a `webarchive <https://web.archive.org/web/20230128102821/https://dev.qubes-os.org/projects/qubes-core-admin/en/latest/>`__
|
||||
|
||||
- `Admin API <https://www.qubes-os.org/news/2017/06/27/qubes-admin-api/>`__ allowing strictly controlled managing from non-dom0
|
||||
|
||||
- All ``qvm-*`` command-line tools rewritten, some options have changed
|
||||
|
||||
- Renaming VM directly is prohibited, there is GUI to clone under new name and remove old VM
|
||||
|
||||
- Use `PVH <https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-037-2018.txt>`__ and `HVM <https://github.com/QubesOS/qubes-issues/issues/2185>`__ by default to `mitigate Meltdown & Spectre <https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-037-2018.txt>`__ and lower the `attack surface on Xen <https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-024-2016.txt>`__
|
||||
|
||||
- Create USB VM by default
|
||||
|
||||
- `Multiple DisposableVMs templates support <https://github.com/QubesOS/qubes-issues/issues/2253>`__
|
||||
|
||||
- New :doc:`backup format </user/how-to-guides/backup-emergency-restore-v4>` using scrypt key-derivation function
|
||||
|
||||
- Non-encrypted backups no longer supported
|
||||
|
||||
- `split VM packages <https://github.com/QubesOS/qubes-issues/issues/2771>`__, for better support minimal, specialized templates
|
||||
|
||||
- `Qubes Manager decomposition <https://github.com/QubesOS/qubes-issues/issues/2132>`__ - domains and devices widgets instead of full Qubes Manager; devices widget support also USB
|
||||
|
||||
- :doc:`More flexible firewall interface </developer/debugging/vm-interface>` for ease unikernel integration
|
||||
|
||||
- Template VMs do not have network interface by default, `qrexec-based updates proxy <https://github.com/QubesOS/qubes-issues/issues/1854>`__ is used instead
|
||||
|
||||
- More flexible IP addressing for VMs - `custom IP <https://github.com/QubesOS/qubes-issues/issues/1477>`__, `hidden from the IP <https://github.com/QubesOS/qubes-issues/issues/1143>`__
|
||||
|
||||
- More flexible Qubes RPC policy - `related ticket <https://github.com/QubesOS/qubes-issues/issues/865>`__, :ref:`documentation <developer/services/qrexec:specifying vms: tags, types, targets, etc.>`
|
||||
|
||||
- `New Qubes RPC confirmation window <https://github.com/QubesOS/qubes-issues/issues/910>`__, including option to specify destination VM
|
||||
|
||||
- `New storage subsystem design <https://github.com/QubesOS/qubes-issues/issues/1842>`__
|
||||
|
||||
- Dom0 update to Fedora 25 for better hardware support
|
||||
|
||||
- Kernel 4.9.x
|
||||
|
||||
|
||||
|
||||
You can get detailed description in `completed github issues <https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+milestone%3A%22Release+4.0%22+label%3Arelease-notes+is%3Aclosed>`__
|
||||
|
||||
Security Notes
|
||||
--------------
|
||||
|
||||
|
||||
- PV VMs migrated from 3.2 to 4.0-rc4 or later are automatically set to PVH mode in order to protect against Meltdown (see `QSB #37 <https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-037-2018.txt>`__). However, PV VMs migrated from any earlier 4.0 release candidate (RC1, RC2, or RC3) are not automatically set to PVH mode. These must be set manually.
|
||||
|
||||
- The following steps may need to be applied in dom0 and Fedora 26 TemplateVMs in order to receive updates (see `#3737 <https://github.com/QubesOS/qubes-issues/issues/3737>`__).
|
||||
Steps for dom0 updates:
|
||||
|
||||
1. Open the Qubes Menu by clicking on the “Q” icon in the top-left corner of the screen.
|
||||
|
||||
2. Select ``Terminal Emulator``.
|
||||
|
||||
3. In the window that opens, enter this command:
|
||||
|
||||
.. code:: bash
|
||||
|
||||
sudo nano /etc/yum.repos.d/qubes-dom0.repo
|
||||
|
||||
|
||||
|
||||
4. This opens the nano text editor. Change all four instances of ``http`` to ``https``.
|
||||
|
||||
5. Press ``CTRL+X``, then ``Y``, then ``ENTER`` to save changes and exit.
|
||||
|
||||
6. Check for updates normally.
|
||||
|
||||
|
||||
Steps for Fedora 26 TemplateVM updates:
|
||||
|
||||
1. Open the Qubes Menu by clicking on the “Q” icon in the top-left corner of the screen.
|
||||
|
||||
2. Select ``Template: fedora-26``, then ``fedora-26: Terminal``.
|
||||
|
||||
3. In the window that opens, enter the command for your version:
|
||||
|
||||
.. code:: bash
|
||||
|
||||
[Qubes 3.2] sudo gedit /etc/yum.repos.d/qubes-r3.repo
|
||||
[Qubes 4.0] sudo gedit /etc/yum.repos.d/qubes-r4.repo
|
||||
|
||||
|
||||
|
||||
4. This opens the gedit text editor in a window. Change all four instances of ``http`` to ``https``.
|
||||
|
||||
5. Click the “Save” button in the top-right corner of the window.
|
||||
|
||||
6. Close the window.
|
||||
|
||||
7. Check for updates normally.
|
||||
|
||||
8. Shut down the TemplateVM.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Known issues
|
||||
------------
|
||||
|
||||
|
||||
- Locale using coma as decimal separator `crashes qubesd <https://github.com/QubesOS/qubes-issues/issues/3753>`__. Either install with different locale (English (United States) for example), or manually apply fix explained in that issue.
|
||||
|
||||
- In the middle of installation, `keyboard layout reset to US <https://github.com/QubesOS/qubes-issues/issues/3352>`__. Be careful what is the current layout while setting default user password (see upper right screen corner).
|
||||
|
||||
- On some laptops (for example Librem 15v2), touchpad do not work directly after installation. Reboot the system to fix the issue.
|
||||
|
||||
- List of USB devices may contain device identifiers instead of name
|
||||
|
||||
- With R4.0.1, which ships kernel-4.19, you may never reach the anaconda startup and be block on an idle black screen with blinking cursor. You can try to add ``plymouth.ignore-serial-consoles`` in the grub installer boot menu right after ``quiet rhgb``. With legacy mode, you can do it directly when booting the DVD or USB key. In UEFI mode, follow the same procedure described for :ref:`disabling <user/troubleshooting/uefi-troubleshooting:installation freezes before displaying installer>` ``nouveau`` module (related `solved issue <https://github.com/QubesOS/qubes-issues/issues/3849>`__ in further version of Qubes).
|
||||
|
||||
- For other known issues take a look at `our tickets <https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+4.0%22+label%3Abug>`__
|
||||
|
||||
|
||||
|
||||
It is advised to install updates just after system installation to apply bug fixes for (some of) the above problems.
|
||||
|
||||
Downloads
|
||||
---------
|
||||
|
||||
|
||||
See `Qubes Downloads <https://www.qubes-os.org/downloads/>`__.
|
||||
|
||||
Installation instructions
|
||||
-------------------------
|
||||
|
||||
|
||||
See :doc:`Installation Guide </user/downloading-installing-upgrading/installation-guide>`.
|
||||
|
||||
Upgrading
|
||||
---------
|
||||
|
||||
|
||||
There is no in-place upgrade path from earlier Qubes versions. The only supported option to upgrade to Qubes R4.0 is to install it from scratch and use :doc:`qubes backup and restore tools </user/how-to-guides/how-to-back-up-restore-and-migrate>` for migrating of all of the user VMs. We also provide :doc:`detailed instruction </user/downloading-installing-upgrading/upgrade/4_0>` for this procedure.
|
||||
|
|
@ -1,28 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/4.0/schedule/
|
||||
redirect_from:
|
||||
- /en/doc/releases/4.0/schedule/
|
||||
ref: 24
|
||||
title: Qubes R4.0 release schedule
|
||||
---
|
||||
|
||||
This schedule is based on [Version Scheme](/doc/version-scheme/#release-schedule).
|
||||
|
||||
| Date | Stage |
|
||||
| -----------:| --------------------------------------- |
|
||||
| 31 Jul 2017 | 4.0-rc1 release |
|
||||
| ~~28 Aug 2017~~ <br/>~~11 Sep 2017~~ <br/>~~9 Oct 2017~~ <br/>18 Oct 2017 | current-testing freeze before 4.0-rc2 |
|
||||
| ~~4 Sep 2017~~ <br/> ~~18 Sep 2017~~ <br/>~~16 Oct 2017~~ <br/>23 Oct 2017 | 4.0-rc2 release |
|
||||
| 6 Nov 2017 | decide whether 4.0-rc2 is the final 4
|
||||
| 20 Nov 2017 | current-testing freeze before 4.0-rc3 |
|
||||
| 27 Nov 2017 | 4.0-rc3 release |
|
||||
| 11 Dec 2017 | decide whether 4.0-rc3 is the final 4.0 |
|
||||
| 1 Jan 2018 | current-testing freeze before 4.0-rc4 |
|
||||
| ~~8 Jan 2018~~ <br/>31 Jan 2018 | 4.0-rc4 release |
|
||||
| ~~22 Jan 2018~~ <br/>14 Feb 2018 | decide whether 4.0-rc4 is the final 4.0 |
|
||||
| 27 Feb 2018 | current-testing freeze before 4.0-rc5 |
|
||||
| 6 Mar 2018 | 4.0-rc5 release |
|
||||
| 20 Mar 2018 | decide whether 4.0-rc5 is the final 4.0 |
|
||||
| 28 Mar 2018 | final 4.0 release |
|
||||
44
developer/releases/4_0/schedule.rst
Normal file
44
developer/releases/4_0/schedule.rst
Normal file
|
|
@ -0,0 +1,44 @@
|
|||
===========================
|
||||
Qubes R4.0 release schedule
|
||||
===========================
|
||||
|
||||
|
||||
This schedule is based on :ref:`Version Scheme <developer/releases/version-scheme:release schedule>`.
|
||||
|
||||
.. list-table::
|
||||
:widths: 88 88
|
||||
:align: center
|
||||
:header-rows: 1
|
||||
|
||||
* - Date
|
||||
- Stage
|
||||
* - 31 Jul 2017
|
||||
- 4.0-rc1 release
|
||||
* - :strike:`28 Aug 2017` :strike:`11 Sep 2017` :strike:`9 Oct 2017` 18 Oct 2017
|
||||
- current-testing freeze before 4.0-rc2
|
||||
* - :strike:`4 Sep 2017` :strike:`18 Sep 2017` :strike:`16 Oct 2017` 23 Oct 2017
|
||||
- 4.0-rc2 release
|
||||
* - 6 Nov 2017
|
||||
- decide whether 4.0-rc2 is the final 4
|
||||
* - 20 Nov 2017
|
||||
- current-testing freeze before 4.0-rc3
|
||||
* - 27 Nov 2017
|
||||
- 4.0-rc3 release
|
||||
* - 11 Dec 2017
|
||||
- decide whether 4.0-rc3 is the final 4.0
|
||||
* - 1 Jan 2018
|
||||
- current-testing freeze before 4.0-rc4
|
||||
* - :strike:`8 Jan 2018` 31 Jan 2018
|
||||
- 4.0-rc4 release
|
||||
* - :strike:`22 Jan 2018` 14 Feb 2018
|
||||
- decide whether 4.0-rc4 is the final 4.0
|
||||
* - 27 Feb 2018
|
||||
- current-testing freeze before 4.0-rc5
|
||||
* - 6 Mar 2018
|
||||
- 4.0-rc5 release
|
||||
* - 20 Mar 2018
|
||||
- decide whether 4.0-rc5 is the final 4.0
|
||||
* - 28 Mar 2018
|
||||
- final 4.0 release
|
||||
|
||||
|
||||
|
|
@ -1,93 +0,0 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Qubes OS 4.1 release notes
|
||||
permalink: /doc/releases/4.1/release-notes/
|
||||
---
|
||||
|
||||
## New features and improvements since Qubes 4.0
|
||||
|
||||
- Optional qubes-remote-support package now available from repositories
|
||||
(strictly opt-in, no package installed by default; no new ports or network
|
||||
connections open by default; requires explicit connection initiation by the
|
||||
user, then requires sharing a code word with the remote party before a
|
||||
connection can be established; see
|
||||
[#6364](https://github.com/QubesOS/qubes-issues/issues/6364) for more
|
||||
information)
|
||||
- Qubes firewall reworked to be more defensive (see
|
||||
[#5540](https://github.com/QubesOS/qubes-issues/issues/5540) for details)
|
||||
- Xen upgraded to version 4.14
|
||||
- Dom0 operating system upgraded to Fedora 32
|
||||
- Default desktop environment upgraded to Xfce 4.14
|
||||
- Upgraded default template releases
|
||||
- Experimental support for GUI running outside of dom0 (hybrid mode GUI domain
|
||||
without real GPU passthrough; see
|
||||
[#5662](https://github.com/QubesOS/qubes-issues/issues/5662) for details)
|
||||
- Experimental support for audio server running outside of dom0 ("Audio domain")
|
||||
- sys-firewall and sys-usb are now disposables by default
|
||||
- UEFI boot now loads GRUB, which in turn loads Xen, making the boot path
|
||||
similar to legacy boot and allowing the user to modify boot parameters or
|
||||
choose an alternate boot menu entry
|
||||
- New qrexec policy format (see
|
||||
[#4370](https://github.com/QubesOS/qubes-issues/issues/4370) for details)
|
||||
- qrexec protocol improvements (see
|
||||
[#4909](https://github.com/QubesOS/qubes-issues/issues/4909) for details)
|
||||
- New qrexec-policy daemon
|
||||
- Simplified using in-qube kernels
|
||||
- Windows USB and audio support courtesy of
|
||||
[tabit-pro](https://github.com/tabit-pro) (see
|
||||
[#5802](https://github.com/QubesOS/qubes-issues/issues/5802) and
|
||||
[#2624](https://github.com/QubesOS/qubes-issues/issues/2624))
|
||||
- Clarified disposable-related terminology and properties
|
||||
- Default kernelopts can now be specified by a kernel package
|
||||
- Improved support for high-resolution displays
|
||||
- Improved notifications when a system drive runs out of free space
|
||||
- Support for different cursor shapes
|
||||
- "Paranoid mode" backup restore option now properly supported using
|
||||
disposables
|
||||
- Users can now choose between Debian and Fedora in the installer
|
||||
- Certain files and applications are now opened in disposables, e.g.,
|
||||
Thunderbird email attachments
|
||||
- New graphical interface for managing testing repository updates
|
||||
- New "Cute Qube" icon family (replaces padlock icons)
|
||||
- Disposable qube types now use the disposable icon
|
||||
- New Template Manager tool for installing, removing, and updating templates
|
||||
(meanwhile, the tool previously known as the "Template Manager," which was
|
||||
for mass template switching, has been integrated into the Qube Manager)
|
||||
- The "file" storage driver has been deprecated in Qubes 4.1 and will be
|
||||
removed in Qubes 4.2
|
||||
- `property-del` event renamed to `property-reset` to avoid confusion
|
||||
- qrexec no longer supports non-executable files in `/etc/qubes-rpc`
|
||||
- qrexec components have been reorganized into the core-qrexec repository
|
||||
- The `qvm-pool` argument parser has been rewritten and improved
|
||||
- Removed the need for the out-of-tree u2mfn kernel module
|
||||
- Qrexec services can now run as a socket server
|
||||
- Improved template distribution mechanism
|
||||
- Now possible to restart qrexec-agent
|
||||
- The term "VM" has largely been replaced by "qube"
|
||||
- GUI daemon is now configured using `qvm-features` tool,
|
||||
`/etc/qubes/guid.conf` file is no longer used
|
||||
- `qvm-run` tool got `--no-shell` option to run a single command without using
|
||||
a shell inside the qube
|
||||
- MAC Randomization for iwlwifi (see [#938](https://github.com/QubesOS/qubes-issues/issues/938))
|
||||
|
||||
For a full list, including more detailed descriptions, please see
|
||||
[here](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+milestone%3A%22Release+4.1%22+label%3A%22release+notes%22+is%3Aclosed).
|
||||
|
||||
## Known issues
|
||||
|
||||
For a full list of known 4.1 issues with open bug reports, please see
|
||||
[here](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+4.1%22+label%3A%22T%3A+bug%22).
|
||||
We strongly recommend [updating Qubes OS](/doc/how-to-update/) immediately
|
||||
after installation in order to apply any and all available bug fixes.
|
||||
|
||||
## Download
|
||||
|
||||
See [downloads](/downloads/).
|
||||
|
||||
## Installation instructions
|
||||
|
||||
See the [installation guide](/doc/installation-guide/).
|
||||
|
||||
## Upgrading
|
||||
|
||||
Please see [how to upgrade to Qubes 4.1](/doc/upgrade/4.1/).
|
||||
116
developer/releases/4_1/release-notes.rst
Normal file
116
developer/releases/4_1/release-notes.rst
Normal file
|
|
@ -0,0 +1,116 @@
|
|||
==========================
|
||||
Qubes OS 4.1 release notes
|
||||
==========================
|
||||
|
||||
|
||||
New features and improvements since Qubes 4.0
|
||||
---------------------------------------------
|
||||
|
||||
|
||||
- Optional qubes-remote-support package now available from repositories (strictly opt-in, no package installed by default; no new ports or network connections open by default; requires explicit connection initiation by the user, then requires sharing a code word with the remote party before a connection can be established; see `#6364 <https://github.com/QubesOS/qubes-issues/issues/6364>`__ for more information)
|
||||
|
||||
- Qubes firewall reworked to be more defensive (see `#5540 <https://github.com/QubesOS/qubes-issues/issues/5540>`__ for details)
|
||||
|
||||
- Xen upgraded to version 4.14
|
||||
|
||||
- Dom0 operating system upgraded to Fedora 32
|
||||
|
||||
- Default desktop environment upgraded to Xfce 4.14
|
||||
|
||||
- Upgraded default template releases
|
||||
|
||||
- Experimental support for GUI running outside of dom0 (hybrid mode GUI domain without real GPU passthrough; see `#5662 <https://github.com/QubesOS/qubes-issues/issues/5662>`__ for details)
|
||||
|
||||
- Experimental support for audio server running outside of dom0 (“Audio domain”)
|
||||
|
||||
- sys-firewall and sys-usb are now disposables by default
|
||||
|
||||
- UEFI boot now loads GRUB, which in turn loads Xen, making the boot path similar to legacy boot and allowing the user to modify boot parameters or choose an alternate boot menu entry
|
||||
|
||||
- New qrexec policy format (see `#4370 <https://github.com/QubesOS/qubes-issues/issues/4370>`__ for details)
|
||||
|
||||
- qrexec protocol improvements (see `#4909 <https://github.com/QubesOS/qubes-issues/issues/4909>`__ for details)
|
||||
|
||||
- New qrexec-policy daemon
|
||||
|
||||
- Simplified using in-qube kernels
|
||||
|
||||
- Windows USB and audio support courtesy of `tabit-pro <https://github.com/tabit-pro>`__ (see `#5802 <https://github.com/QubesOS/qubes-issues/issues/5802>`__ and `#2624 <https://github.com/QubesOS/qubes-issues/issues/2624>`__)
|
||||
|
||||
- Clarified disposable-related terminology and properties
|
||||
|
||||
- Default kernelopts can now be specified by a kernel package
|
||||
|
||||
- Improved support for high-resolution displays
|
||||
|
||||
- Improved notifications when a system drive runs out of free space
|
||||
|
||||
- Support for different cursor shapes
|
||||
|
||||
- “Paranoid mode” backup restore option now properly supported using disposables
|
||||
|
||||
- Users can now choose between Debian and Fedora in the installer
|
||||
|
||||
- Certain files and applications are now opened in disposables, e.g., Thunderbird email attachments
|
||||
|
||||
- New graphical interface for managing testing repository updates
|
||||
|
||||
- New “Cute Qube” icon family (replaces padlock icons)
|
||||
|
||||
- Disposable qube types now use the disposable icon
|
||||
|
||||
- New Template Manager tool for installing, removing, and updating templates (meanwhile, the tool previously known as the “Template Manager,” which was for mass template switching, has been integrated into the Qube Manager)
|
||||
|
||||
- The “file” storage driver has been deprecated in Qubes 4.1 and will be removed in Qubes 4.2
|
||||
|
||||
- ``property-del`` event renamed to ``property-reset`` to avoid confusion
|
||||
|
||||
- qrexec no longer supports non-executable files in ``/etc/qubes-rpc``
|
||||
|
||||
- qrexec components have been reorganized into the core-qrexec repository
|
||||
|
||||
- The ``qvm-pool`` argument parser has been rewritten and improved
|
||||
|
||||
- Removed the need for the out-of-tree u2mfn kernel module
|
||||
|
||||
- Qrexec services can now run as a socket server
|
||||
|
||||
- Improved template distribution mechanism
|
||||
|
||||
- Now possible to restart qrexec-agent
|
||||
|
||||
- The term “VM” has largely been replaced by “qube”
|
||||
|
||||
- GUI daemon is now configured using ``qvm-features`` tool, ``/etc/qubes/guid.conf`` file is no longer used
|
||||
|
||||
- ``qvm-run`` tool got ``--no-shell`` option to run a single command without using a shell inside the qube
|
||||
|
||||
- MAC Randomization for iwlwifi (see `#938 <https://github.com/QubesOS/qubes-issues/issues/938>`__)
|
||||
|
||||
|
||||
|
||||
For a full list, including more detailed descriptions, please see `here <https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+milestone%3A%22Release+4.1%22+label%3A%22release+notes%22+is%3Aclosed>`__.
|
||||
|
||||
Known issues
|
||||
------------
|
||||
|
||||
|
||||
For a full list of known 4.1 issues with open bug reports, please see `here <https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+4.1%22+label%3A%22T%3A+bug%22>`__. We strongly recommend :doc:`updating Qubes OS </user/how-to-guides/how-to-update>` immediately after installation in order to apply any and all available bug fixes.
|
||||
|
||||
Download
|
||||
--------
|
||||
|
||||
|
||||
See `downloads <https://www.qubes-os.org/downloads/>`__.
|
||||
|
||||
Installation instructions
|
||||
-------------------------
|
||||
|
||||
|
||||
See the :doc:`installation guide </user/downloading-installing-upgrading/installation-guide>`.
|
||||
|
||||
Upgrading
|
||||
---------
|
||||
|
||||
|
||||
Please see :doc:`how to upgrade to Qubes 4.1 </user/downloading-installing-upgrading/upgrade/4_1>`.
|
||||
|
|
@ -1,25 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/4.1/schedule/
|
||||
redirect_from:
|
||||
- /en/doc/releases/4.1/schedule/
|
||||
title: Qubes R4.1 release schedule
|
||||
---
|
||||
|
||||
The table below is based on our [release schedule
|
||||
policy](/doc/version-scheme/#release-schedule).
|
||||
|
||||
| Date | Stage |
|
||||
| ----------:| ----------------------------------------- |
|
||||
| 2021-10-11 | 4.1.0-rc1 release |
|
||||
| 2021-11-08 | current-testing freeze before 4.1.0-rc2 |
|
||||
| 2021-11-15 | 4.1.0-rc2 release |
|
||||
| 2021-11-29 | decide whether 4.1.0-rc2 is the final 4.1 |
|
||||
| 2021-12-13 | current-testing freeze before 4.1.0-rc3 |
|
||||
| 2021-12-20 | 4.1.0-rc3 release |
|
||||
| 2022-01-03 | decide whether 4.1.0-rc3 is the final 4.1 |
|
||||
| 2022-01-11 | current-testing freeze before 4.1.0-rc4 |
|
||||
| 2022-01-18 | 4.1.0-rc4 release |
|
||||
| 2022-01-31 | decide whether 4.1.0-rc4 is the final 4.1 |
|
||||
| 2022-02-04 | final 4.1.0 release |
|
||||
38
developer/releases/4_1/schedule.rst
Normal file
38
developer/releases/4_1/schedule.rst
Normal file
|
|
@ -0,0 +1,38 @@
|
|||
===========================
|
||||
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
|
||||
:align: center
|
||||
:header-rows: 1
|
||||
|
||||
* - Date
|
||||
- Stage
|
||||
* - 2021-10-11
|
||||
- 4.1.0-rc1 release
|
||||
* - 2021-11-08
|
||||
- current-testing freeze before 4.1.0-rc2
|
||||
* - 2021-11-15
|
||||
- 4.1.0-rc2 release
|
||||
* - 2021-11-29
|
||||
- decide whether 4.1.0-rc2 is the final 4.1
|
||||
* - 2021-12-13
|
||||
- current-testing freeze before 4.1.0-rc3
|
||||
* - 2021-12-20
|
||||
- 4.1.0-rc3 release
|
||||
* - 2022-01-03
|
||||
- decide whether 4.1.0-rc3 is the final 4.1
|
||||
* - 2022-01-11
|
||||
- current-testing freeze before 4.1.0-rc4
|
||||
* - 2022-01-18
|
||||
- 4.1.0-rc4 release
|
||||
* - 2022-01-31
|
||||
- decide whether 4.1.0-rc4 is the final 4.1
|
||||
* - 2022-02-04
|
||||
- final 4.1.0 release
|
||||
|
||||
|
||||
|
|
@ -1,84 +0,0 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Qubes OS 4.2 release notes
|
||||
permalink: /doc/releases/4.2/release-notes/
|
||||
---
|
||||
|
||||
## New features and improvements since Qubes 4.1
|
||||
|
||||
- Dom0 upgraded to Fedora 37 ([#6982](https://github.com/QubesOS/qubes-issues/issues/6982))
|
||||
- Xen upgraded to version 4.17
|
||||
- Default Debian template upgraded to Debian 12
|
||||
- Default Fedora and Debian templates use Xfce instead of GNOME ([#7784](https://github.com/QubesOS/qubes-issues/issues/7784))
|
||||
- SELinux support in Fedora templates ([#4239](https://github.com/QubesOS/qubes-issues/issues/4239))
|
||||
- Several GUI applications rewritten (screenshots below), including:
|
||||
- Applications Menu (also available as preview in R4.1) ([#6665](https://github.com/QubesOS/qubes-issues/issues/6665)), ([#5677](https://github.com/QubesOS/qubes-issues/issues/5677))
|
||||
- Qubes Global Settings ([#6898](https://github.com/QubesOS/qubes-issues/issues/6898))
|
||||
- Create New Qube
|
||||
- Qubes Update ([#7443](https://github.com/QubesOS/qubes-issues/issues/7443))
|
||||
- New `qubes-vm-update` tool ([#7443](https://github.com/QubesOS/qubes-issues/issues/7443))
|
||||
- Unified `grub.cfg` location for both UEFI and legacy boot ([#7985](https://github.com/QubesOS/qubes-issues/issues/7985))
|
||||
- PipeWire support ([#6358](https://github.com/QubesOS/qubes-issues/issues/6358))
|
||||
- fwupd integration for firmware updates ([#4855](https://github.com/QubesOS/qubes-issues/issues/4855))
|
||||
- Optional automatic clipboard clearing ([#3415](https://github.com/QubesOS/qubes-issues/issues/3415))
|
||||
- Official packages built using Qubes Builder v2 ([#6486](https://github.com/QubesOS/qubes-issues/issues/6486))
|
||||
- Split GPG management in Qubes Global Settings
|
||||
- Qrexec services use new qrexec policy format by default (but old format is still supported) ([#8000](https://github.com/QubesOS/qubes-issues/issues/8000))
|
||||
- Improved keyboard layout switching
|
||||
|
||||
For a full list, including more detailed descriptions, please see [here](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+milestone%3A%22Release+4.2%22+label%3A%22release+notes%22+is%3Aclosed). Below are some screenshots of the new and improved Qubes GUI tools.
|
||||
|
||||
The new Qubes OS Update tool:
|
||||
|
||||
[](/attachment/site/4-2_update.png)
|
||||
|
||||
The new Qubes OS Global Config tool:
|
||||
|
||||
[](/attachment/site/4-2_global-config_1.png)
|
||||
[](/attachment/site/4-2_global-config_2.png)
|
||||
|
||||
The new Qubes OS Policy Editor tool:
|
||||
|
||||
[](/attachment/site/4-2_policy-editor.png)
|
||||
|
||||
## Known issues
|
||||
|
||||
- DomU firewalls have completely switched to nftables. Users should add their custom rules to the `custom-input` and `custom-forward` chains. (For more information, see issues [#5031](https://github.com/QubesOS/qubes-issues/issues/5031) and [#6062](https://github.com/QubesOS/qubes-issues/issues/6062).)
|
||||
|
||||
- Templates restored in 4.2 from a pre-4.2 backup continue to target their original Qubes OS release repos. If you are using fresh templates on a clean 4.2 installation, or if you performed an [in-place upgrade from 4.1 to 4.2](/doc/upgrade/4.2/#in-place-upgrade), then this does not affect you. (For more information, see issue [#8701](https://github.com/QubesOS/qubes-issues/issues/8701).)
|
||||
|
||||
Also see the [full list of open bug reports affecting Qubes 4.2](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+label%3Aaffects-4.2+label%3A%22T%3A+bug%22+is%3Aopen).
|
||||
|
||||
We strongly recommend [updating Qubes OS](/doc/how-to-update/) immediately after installation in order to apply all available bug fixes.
|
||||
|
||||
## Notes
|
||||
|
||||
- Qubes 4.2 does not support Debian 11 templates (see [supported template releases](/doc/supported-releases/#templates)). Please [upgrade your Debian templates](/doc/templates/debian/#upgrading) to Debian 12.
|
||||
|
||||
- Qubes 4.2.2 includes a fix for [#8332: File-copy qrexec service is overly restrictive](https://github.com/QubesOS/qubes-issues/issues/8332). As explained in the issue comments, we introduced a change in Qubes 4.2.0 that caused inter-qube file-copy/move actions to reject filenames containing, e.g., non-Latin characters and certain symbols. The rationale for this change was to mitigate the security risks associated with unusual unicode characters and invalid encoding in filenames, which some software might handle in an unsafe manner and which might cause confusion for users. Such a change represents a trade-off between security and usability.
|
||||
|
||||
- After the change went live, we received several user reports indicating more severe usability problems than we had anticipated. Moreover, these problems were prompting users to resort to dangerous workarounds (such as packing files into an archive format prior to copying) that carry far more risk than the original risk posed by the unrestricted filenames. In addition, we realized that this was a backward-incompatible change that should not have been introduced in a minor release in the first place.
|
||||
|
||||
- Therefore, we have decided, for the time being, to restore the original (pre-4.2) behavior by introducing a new `allow-all-names` argument for the `qubes.Filecopy` service. By default, `qvm-copy` and similar tools will use this less restrictive service (`qubes.Filecopy +allow-all-names`) whenever they detect any files that would be have been blocked by the more restrictive service (`qubes.Filecopy +`). If no such files are detected, they will use the more restrictive service.
|
||||
|
||||
- Users who wish to opt for the more restrictive 4.2.0 and 4.2.1 behavior can do so by modifying their RPC policy rules. To switch a single rule to the more restrictive behavior, change `*` in the argument column to `+` (i.e., change "any argument" to "only empty"). To use the more restrictive behavior globally, add the following "deny" rule before all other relevant rules:
|
||||
|
||||
```
|
||||
qubes.Filecopy +allow-all-names @anyvm @anyvm deny
|
||||
```
|
||||
|
||||
- For more information, see [RPC policies](/doc/rpc-policy/) and [Qube configuration interface](/doc/vm-interface/#qubes-rpc).
|
||||
|
||||
- Beginning with Qubes 4.2, the recommended way to update Qubes OS via the command line has changed. Salt is no longer the preferred method, though it is still supported. Instead, `qubes-dom0-update` is recommended for updating dom0, and `qubes-vm-update` is recommended for updating templates and standalones. (The recommended way to update via the GUI has not changed. The Qubes Update tool is still the preferred method.) For more information, see [How to update](/doc/how-to-update/).
|
||||
|
||||
## Download
|
||||
|
||||
All Qubes ISOs and associated [verification files](/security/verifying-signatures/) are available on the [downloads](/downloads/) page.
|
||||
|
||||
## Installation instructions
|
||||
|
||||
See the [installation guide](/doc/installation-guide/).
|
||||
|
||||
## Upgrading
|
||||
|
||||
Please see [how to upgrade to Qubes 4.2](/doc/upgrade/4.2/).
|
||||
136
developer/releases/4_2/release-notes.rst
Normal file
136
developer/releases/4_2/release-notes.rst
Normal file
|
|
@ -0,0 +1,136 @@
|
|||
==========================
|
||||
Qubes OS 4.2 release notes
|
||||
==========================
|
||||
|
||||
|
||||
New features and improvements since Qubes 4.1
|
||||
---------------------------------------------
|
||||
|
||||
|
||||
- Dom0 upgraded to Fedora 37 (`#6982 <https://github.com/QubesOS/qubes-issues/issues/6982>`__)
|
||||
|
||||
- Xen upgraded to version 4.17
|
||||
|
||||
- Default Debian template upgraded to Debian 12
|
||||
|
||||
- Default Fedora and Debian templates use Xfce instead of GNOME (`#7784 <https://github.com/QubesOS/qubes-issues/issues/7784>`__)
|
||||
|
||||
- SELinux support in Fedora templates (`#4239 <https://github.com/QubesOS/qubes-issues/issues/4239>`__)
|
||||
|
||||
- Several GUI applications rewritten (screenshots below), including:
|
||||
|
||||
- Applications Menu (also available as preview in R4.1) (`#6665 <https://github.com/QubesOS/qubes-issues/issues/6665>`__), (`#5677 <https://github.com/QubesOS/qubes-issues/issues/5677>`__)
|
||||
|
||||
- Qubes Global Settings (`#6898 <https://github.com/QubesOS/qubes-issues/issues/6898>`__)
|
||||
|
||||
- Create New Qube
|
||||
|
||||
- Qubes Update (`#7443 <https://github.com/QubesOS/qubes-issues/issues/7443>`__)
|
||||
|
||||
|
||||
|
||||
- New ``qubes-vm-update`` tool (`#7443 <https://github.com/QubesOS/qubes-issues/issues/7443>`__)
|
||||
|
||||
- Unified ``grub.cfg`` location for both UEFI and legacy boot (`#7985 <https://github.com/QubesOS/qubes-issues/issues/7985>`__)
|
||||
|
||||
- PipeWire support (`#6358 <https://github.com/QubesOS/qubes-issues/issues/6358>`__)
|
||||
|
||||
- fwupd integration for firmware updates (`#4855 <https://github.com/QubesOS/qubes-issues/issues/4855>`__)
|
||||
|
||||
- Optional automatic clipboard clearing (`#3415 <https://github.com/QubesOS/qubes-issues/issues/3415>`__)
|
||||
|
||||
- Official packages built using Qubes Builder v2 (`#6486 <https://github.com/QubesOS/qubes-issues/issues/6486>`__)
|
||||
|
||||
- Split GPG management in Qubes Global Settings
|
||||
|
||||
- Qrexec services use new qrexec policy format by default (but old format is still supported) (`#8000 <https://github.com/QubesOS/qubes-issues/issues/8000>`__)
|
||||
|
||||
- Improved keyboard layout switching
|
||||
|
||||
|
||||
|
||||
For a full list, including more detailed descriptions, please see `here <https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+milestone%3A%22Release+4.2%22+label%3A%22release+notes%22+is%3Aclosed>`__. Below are some screenshots of the new and improved Qubes GUI tools.
|
||||
|
||||
The new Qubes OS Update tool:
|
||||
|
||||
|Screenshot of the Qubes OS Update tool|
|
||||
|
||||
The new Qubes OS Global Config tool:
|
||||
|
||||
|Screenshot of the Qubes OS Global Config tool| |image1|
|
||||
|
||||
The new Qubes OS Policy Editor tool:
|
||||
|
||||
|Screenshot of the Qubes OS Policy Editor tool|
|
||||
|
||||
Known issues
|
||||
------------
|
||||
|
||||
|
||||
- DomU firewalls have completely switched to nftables. Users should add their custom rules to the ``custom-input`` and ``custom-forward`` chains. (For more information, see issues `#5031 <https://github.com/QubesOS/qubes-issues/issues/5031>`__ and `#6062 <https://github.com/QubesOS/qubes-issues/issues/6062>`__.)
|
||||
|
||||
- Templates restored in 4.2 from a pre-4.2 backup continue to target their original Qubes OS release repos. If you are using fresh templates on a clean 4.2 installation, or if you performed an :ref:`in-place upgrade from 4.1 to 4.2 <user/downloading-installing-upgrading/upgrade/4_2:in-place upgrade>`, then this does not affect you. (For more information, see issue `#8701 <https://github.com/QubesOS/qubes-issues/issues/8701>`__.)
|
||||
|
||||
|
||||
|
||||
Also see the `full list of open bug reports affecting Qubes 4.2 <https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+label%3Aaffects-4.2+label%3A%22T%3A+bug%22+is%3Aopen>`__.
|
||||
|
||||
We strongly recommend :doc:`updating Qubes OS </user/how-to-guides/how-to-update>` immediately after installation in order to apply all available bug fixes.
|
||||
|
||||
Notes
|
||||
-----
|
||||
|
||||
|
||||
- Qubes 4.2 does not support Debian 11 templates (see :ref:`supported template releases <user/downloading-installing-upgrading/supported-releases:templates>`). Please :ref:`upgrade your Debian templates <user/templates/debian/debian:upgrading>` to Debian 12.
|
||||
|
||||
- Qubes 4.2.2 includes a fix for `#8332: File-copy qrexec service is overly restrictive <https://github.com/QubesOS/qubes-issues/issues/8332>`__. As explained in the issue comments, we introduced a change in Qubes 4.2.0 that caused inter-qube file-copy/move actions to reject filenames containing, e.g., non-Latin characters and certain symbols. The rationale for this change was to mitigate the security risks associated with unusual unicode characters and invalid encoding in filenames, which some software might handle in an unsafe manner and which might cause confusion for users. Such a change represents a trade-off between security and usability.
|
||||
|
||||
- After the change went live, we received several user reports indicating more severe usability problems than we had anticipated. Moreover, these problems were prompting users to resort to dangerous workarounds (such as packing files into an archive format prior to copying) that carry far more risk than the original risk posed by the unrestricted filenames. In addition, we realized that this was a backward-incompatible change that should not have been introduced in a minor release in the first place.
|
||||
|
||||
- Therefore, we have decided, for the time being, to restore the original (pre-4.2) behavior by introducing a new ``allow-all-names`` argument for the ``qubes.Filecopy`` service. By default, ``qvm-copy`` and similar tools will use this less restrictive service (``qubes.Filecopy +allow-all-names``) whenever they detect any files that would be have been blocked by the more restrictive service (``qubes.Filecopy +``). If no such files are detected, they will use the more restrictive service.
|
||||
|
||||
- Users who wish to opt for the more restrictive 4.2.0 and 4.2.1 behavior can do so by modifying their RPC policy rules. To switch a single rule to the more restrictive behavior, change ``*`` in the argument column to ``+`` (i.e., change “any argument” to “only empty”). To use the more restrictive behavior globally, add the following “deny” rule before all other relevant rules:
|
||||
|
||||
.. code:: bash
|
||||
|
||||
qubes.Filecopy +allow-all-names @anyvm @anyvm deny
|
||||
|
||||
|
||||
|
||||
- For more information, see :doc:`RPC policies </user/advanced-topics/rpc-policy>` and :ref:`Qube configuration interface <developer/debugging/vm-interface:qubes rpc>`.
|
||||
|
||||
|
||||
|
||||
- Beginning with Qubes 4.2, the recommended way to update Qubes OS via the command line has changed. Salt is no longer the preferred method, though it is still supported. Instead, ``qubes-dom0-update`` is recommended for updating dom0, and ``qubes-vm-update`` is recommended for updating templates and standalones. (The recommended way to update via the GUI has not changed. The Qubes Update tool is still the preferred method.) For more information, see :doc:`How to update </user/how-to-guides/how-to-update>`.
|
||||
|
||||
|
||||
|
||||
Download
|
||||
--------
|
||||
|
||||
|
||||
All Qubes ISOs and associated :doc:`verification files </project-security/verifying-signatures>` are available on the `downloads <https://www.qubes-os.org/downloads/>`__ page.
|
||||
|
||||
Installation instructions
|
||||
-------------------------
|
||||
|
||||
|
||||
See the :doc:`installation guide </user/downloading-installing-upgrading/installation-guide>`.
|
||||
|
||||
Upgrading
|
||||
---------
|
||||
|
||||
|
||||
Please see :doc:`how to upgrade to Qubes 4.2 </user/downloading-installing-upgrading/upgrade/4_2>`.
|
||||
|
||||
.. |Screenshot of the Qubes OS Update tool| image:: /attachment/site/4-2_update.png
|
||||
|
||||
|
||||
.. |Screenshot of the Qubes OS Global Config tool| image:: /attachment/site/4-2_global-config_1.png
|
||||
|
||||
|
||||
.. |image1| image:: /attachment/site/4-2_global-config_2.png
|
||||
|
||||
|
||||
.. |Screenshot of the Qubes OS Policy Editor tool| image:: /attachment/site/4-2_policy-editor.png
|
||||
|
||||
|
|
@ -1,20 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/4.2/schedule/
|
||||
redirect_from:
|
||||
- /en/doc/releases/4.2/schedule/
|
||||
title: 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 [release schedule
|
||||
policy](/doc/version-scheme/#release-schedule).
|
||||
|
||||
| Date | Stage |
|
||||
| ----------:| ----------------------------------------- |
|
||||
| 2023-06-02 | 4.2.0-rc1 release |
|
||||
| 2023-08-28 | 4.2.0-rc2 release |
|
||||
| 2023-09-03 | 4.2.0-rc3 release |
|
||||
| 2023-10-13 | 4.2.0-rc4 release |
|
||||
26
developer/releases/4_2/schedule.rst
Normal file
26
developer/releases/4_2/schedule.rst
Normal file
|
|
@ -0,0 +1,26 @@
|
|||
===========================
|
||||
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>`.
|
||||
|
||||
.. list-table::
|
||||
:widths: 10 10
|
||||
:align: center
|
||||
:header-rows: 1
|
||||
|
||||
* - Date
|
||||
- Stage
|
||||
* - 2023-06-02
|
||||
- 4.2.0-rc1 release
|
||||
* - 2023-08-28
|
||||
- 4.2.0-rc2 release
|
||||
* - 2023-09-03
|
||||
- 4.2.0-rc3 release
|
||||
* - 2023-10-13
|
||||
- 4.2.0-rc4 release
|
||||
|
||||
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/notes/
|
||||
ref: 13
|
||||
title: Release notes
|
||||
---
|
||||
|
||||
- [Qubes R1.0 release notes](/doc/releases/1.0/release-notes/)
|
||||
- [Qubes R2.0 release notes](/doc/releases/2.0/release-notes/)
|
||||
- [Qubes R3.0 release notes](/doc/releases/3.0/release-notes/)
|
||||
- [Qubes R3.1 release notes](/doc/releases/3.1/release-notes/)
|
||||
- [Qubes R3.2 release notes](/doc/releases/3.2/release-notes/)
|
||||
- [Qubes R4.0 release notes](/doc/releases/4.0/release-notes/)
|
||||
- [Qubes R4.1 release notes](/doc/releases/4.1/release-notes/)
|
||||
- [Qubes R4.2 release notes](/doc/releases/4.2/release-notes/)
|
||||
25
developer/releases/notes.rst
Normal file
25
developer/releases/notes.rst
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
=============
|
||||
Release notes
|
||||
=============
|
||||
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
Qubes R1.0 release notes </developer/releases/1_0/release-notes>
|
||||
|
||||
Qubes R2.0 release notes </developer/releases/2_0/release-notes>
|
||||
|
||||
Qubes R3.0 release notes </developer/releases/3_0/release-notes>
|
||||
|
||||
Qubes R3.1 release notes </developer/releases/3_1/release-notes>
|
||||
|
||||
Qubes R3.2 release notes </developer/releases/3_2/release-notes>
|
||||
|
||||
Qubes R4.0 release notes </developer/releases/4_0/release-notes>
|
||||
|
||||
Qubes R4.1 release notes </developer/releases/4_1/release-notes>
|
||||
|
||||
Qubes R4.2 release notes </developer/releases/4_2/release-notes>
|
||||
|
||||
|
||||
|
|
@ -1,14 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/schedules/
|
||||
ref: 15
|
||||
title: Release schedules
|
||||
---
|
||||
|
||||
- [Qubes R3.0 release schedule](/doc/releases/3.0/schedule/)
|
||||
- [Qubes R3.1 release schedule](/doc/releases/3.1/schedule/)
|
||||
- [Qubes R3.2 release schedule](/doc/releases/3.2/schedule/)
|
||||
- [Qubes R4.0 release schedule](/doc/releases/4.0/schedule/)
|
||||
- [Qubes R4.1 release schedule](/doc/releases/4.1/schedule/)
|
||||
- [Qubes R4.2 release schedule](/doc/releases/4.2/schedule/)
|
||||
21
developer/releases/schedules.rst
Normal file
21
developer/releases/schedules.rst
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
=================
|
||||
Release schedules
|
||||
=================
|
||||
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
Qubes R3.0 release schedule </developer/releases/3_0/schedule>
|
||||
|
||||
Qubes R3.1 release schedule </developer/releases/3_1/schedule>
|
||||
|
||||
Qubes R3.2 release schedule </developer/releases/3_2/schedule>
|
||||
|
||||
Qubes R4.0 release schedule </developer/releases/4_0/schedule>
|
||||
|
||||
Qubes R4.1 release schedule </developer/releases/4_1/schedule>
|
||||
|
||||
Qubes R4.2 release schedule </developer/releases/4_2/schedule>
|
||||
|
||||
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/releases/todo/
|
||||
redirect_from:
|
||||
- /en/doc/releases/todo/
|
||||
ref: 14
|
||||
title: Release checklist
|
||||
---
|
||||
|
||||
*the checklist is probably unfinished*
|
||||
|
||||
On -rc1
|
||||
-------
|
||||
|
||||
* write schedule
|
||||
* create package repositories (linux-yum, linux-deb)
|
||||
* update repository definition (core-agent-linux, installer-qubes-os/qubes-release)
|
||||
* push all packages to `current-testing`
|
||||
* draft release notes, one note per feature
|
||||
* create upgrade package in previous release branch (r2->r3.0, r3.0->r3.1, etc) - core-agent-linux
|
||||
* make sure that keys for the current release are included in previous release's qubes-release package (for upgrade)
|
||||
* build ISO and push to mirrors
|
||||
|
||||
On subsequent -rc
|
||||
-----------------
|
||||
|
||||
* push packages to `current`
|
||||
* update release notes
|
||||
* build ISO and push to mirrors
|
||||
* notify @Rudd-O about the new ISO for new torrent hosting
|
||||
|
||||
On final release
|
||||
----------------
|
||||
|
||||
* push packages to `current`
|
||||
* finish release notes
|
||||
* update InstallationInstructions
|
||||
* build ISO and push to mirrors
|
||||
* push `qubes-release` package to `current`
|
||||
* notify @Rudd-O about the new ISO for new torrent hosting
|
||||
* write news post
|
||||
* announce
|
||||
64
developer/releases/todo.rst
Normal file
64
developer/releases/todo.rst
Normal file
|
|
@ -0,0 +1,64 @@
|
|||
=================
|
||||
Release checklist
|
||||
=================
|
||||
|
||||
|
||||
*the checklist is probably unfinished*
|
||||
|
||||
On -rc1
|
||||
-------
|
||||
|
||||
|
||||
- write schedule
|
||||
|
||||
- create package repositories (linux-yum, linux-deb)
|
||||
|
||||
- update repository definition (core-agent-linux, installer-qubes-os/qubes-release)
|
||||
|
||||
- push all packages to ``current-testing``
|
||||
|
||||
- draft release notes, one note per feature
|
||||
|
||||
- create upgrade package in previous release branch (r2->r3.0, r3.0->r3.1, etc) - core-agent-linux
|
||||
|
||||
- make sure that keys for the current release are included in previous release’s qubes-release package (for upgrade)
|
||||
|
||||
- build ISO and push to mirrors
|
||||
|
||||
|
||||
|
||||
On subsequent -rc
|
||||
-----------------
|
||||
|
||||
|
||||
- push packages to ``current``
|
||||
|
||||
- update release notes
|
||||
|
||||
- build ISO and push to mirrors
|
||||
|
||||
- notify @Rudd-O about the new ISO for new torrent hosting
|
||||
|
||||
|
||||
|
||||
On final release
|
||||
----------------
|
||||
|
||||
|
||||
- push packages to ``current``
|
||||
|
||||
- finish release notes
|
||||
|
||||
- update InstallationInstructions
|
||||
|
||||
- build ISO and push to mirrors
|
||||
|
||||
- push ``qubes-release`` package to ``current``
|
||||
|
||||
- notify @Rudd-O about the new ISO for new torrent hosting
|
||||
|
||||
- write news post
|
||||
|
||||
- announce
|
||||
|
||||
|
||||
|
|
@ -1,189 +0,0 @@
|
|||
---
|
||||
lang: en
|
||||
layout: doc
|
||||
permalink: /doc/version-scheme/
|
||||
redirect_from:
|
||||
- /en/doc/version-scheme/
|
||||
- /doc/VersionScheme/
|
||||
- /wiki/VersionScheme/
|
||||
ref: 151
|
||||
title: Version scheme
|
||||
---
|
||||
|
||||
The Qubes OS Project uses the [semantic versioning](https://semver.org/)
|
||||
standard. Version numbers are written as `<major>.<minor>.<patch>`. When
|
||||
`<patch>` is omitted (e.g., `4.1`), it is usually either because `<patch>` is
|
||||
zero (as in `4.1.0`) or because we are referring to a specific minor release
|
||||
irrespective of any particular patch release within it. Similarly, the major
|
||||
release number alone (e.g., `R4`) is sometimes used to refer to an entire
|
||||
release series inclusive of all minor and patch releases within it.
|
||||
|
||||
In general, patch releases are for backward-compatible bug fixes, minor
|
||||
releases are for backward-compatible enhancements and new features, and major
|
||||
release are for any backward-incompatible changes. This means that, in general,
|
||||
one should *not* try to introduce features or enhancements in patch releases or
|
||||
any backward-incompatible changes in patch or minor releases. (Templates are a
|
||||
notable exception, as upstream OSes almost always have their own release
|
||||
schedules.) Bug fixes are allowed in all releases, and backward-compatible
|
||||
changes are allowed in all major and minor releases.
|
||||
|
||||
Qubes OS minor releases generally include new features, new templates, and
|
||||
occasionally new defaults, but they are still backward-compatible in the sense
|
||||
that qubes and features that worked in the previous release still function,
|
||||
though the UI may be different in some cases. In general, deprecated features
|
||||
are removed only in major releases, and in-place upgrades between major versions
|
||||
are not guaranteed.
|
||||
|
||||
Following standard practice, **version** refers to any build that has been
|
||||
assigned a version name or number, e.g., `3.2-rc2`, `4.0.4`, `4.1-beta1`. By
|
||||
contrast, **release** refers to any version that is intended for consumption by
|
||||
the general userbase. For example, `4.0.4` was both a **version** and a
|
||||
**release**, since it was stable and intended for general public use, while
|
||||
`4.1-beta1` was a **version** but *not* a **release**, since it was not stable
|
||||
and was intended only for [testing](/doc/testing/). All releases are
|
||||
versions, but not all versions are releases.
|
||||
|
||||
The letter **R**, as in `R4.1`, stands for **release**. The abbreviation **RC**,
|
||||
as in `3.2-rc2`, stands for **release candidate**.
|
||||
|
||||
## Qubes distributions and products
|
||||
|
||||
We intend to make it easy to make a remix of Qubes, targeting another
|
||||
hypervisor or isolation provider. We may also create commercial products
|
||||
intended for specific circumstances. There is one distinguished distribution
|
||||
called **Qubes OS**. All source code for it is available for download under a
|
||||
[free and open-source license](/doc/license/) and is openly developed on
|
||||
[GitHub](https://github.com/QubesOS) and our [mailing
|
||||
lists](https://www.qubes-os.org/support/). The rest of this document discusses
|
||||
Qubes OS. Another remix may have its own version series.
|
||||
|
||||
## Release versioning
|
||||
|
||||
Qubes OS as a whole is released from time to time. When preparing a new release,
|
||||
we decide on the `<major>.<minor>` numbers (e.g., `3.0`, which is short for
|
||||
`3.0.0`). We then publish the first release candidate, e.g., `3.0.0-rc1`. When
|
||||
we feel that enough progress has been made, we'll release `3.0.0-rc2` and so on.
|
||||
All these versions (which are not yet releases) are considered unstable and are
|
||||
not intended for production use. You are welcome to [help us
|
||||
test](/doc/testing/) these versions.
|
||||
|
||||
When enough progress has been made, we announce the first stable release, e.g.
|
||||
`3.0.0`. This is not only a version but an actual release. It is considered
|
||||
stable, and we commit to supporting it according to our [support
|
||||
schedule](/doc/supported-releases/). Core components are branched at this
|
||||
moment, and bug fixes are backported from the main branch. Please see [help,
|
||||
support, mailing lists, and forum](/support/) for places to ask questions about
|
||||
stable releases. No major features or interface incompatibilities are to be
|
||||
included in this release. We release bug fixes as patch releases (`3.0.1`,
|
||||
`3.0.2`, and so on), while backward-compatible enhancements and new features
|
||||
are introduced in the next minor release (e.g., `3.1`). Any
|
||||
backward-incompatible changes are introduced in the next major release (e.g.,
|
||||
`4.0`).
|
||||
|
||||
Please see [issue tracking](/doc/issue-tracking/) for information about how
|
||||
releases are handled in the issue tracker.
|
||||
|
||||
## Release schedule
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
| Stage | Duration |
|
||||
| ------------------------ | --------- |
|
||||
| initial testing | two weeks |
|
||||
| bug fixing | 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.
|
||||
|
||||
[](/attachment/doc/release-cycle.svg)
|
||||
|
||||
## Bug priorities
|
||||
|
||||
When deciding whether the current release candidate is the final one, the
|
||||
Committee takes bug [priorities](/doc/issue-tracking/#priority) into
|
||||
consideration. The meaning of them is as follows:
|
||||
|
||||
- `blocker` --- when any such bug is present in the current release candidate,
|
||||
it can't be considered final release. Bugs with this priority must be fixed
|
||||
before the next release candidate, even if that means delaying its release
|
||||
(which should be considered only last resort option).
|
||||
|
||||
- `critical` --- when any such bug is present in the current release candidate,
|
||||
it can't be considered final release. But such bugs are not qualified to
|
||||
delay next release candidate release.
|
||||
|
||||
- `major` --- existence of such bugs do not strictly prevent the current
|
||||
release candidate be considered final (but of course we should try hard to
|
||||
not have them there). Fixing bugs of this priority can be delayed and
|
||||
qualified as updates to the final stable release.
|
||||
|
||||
- `default` and `minor` --- existence of such bugs do not prevent the current
|
||||
release candidate be considered final. Fixing such bugs can be delayed to the
|
||||
next Qubes OS release. Eventually such fixes might be backported as an update
|
||||
to the stable release(s). (`default` should really be assigned a more
|
||||
specific priority, but in practice there are too many issues and not enough
|
||||
time, so `default` ends up staying on many issues.)
|
||||
|
||||
All above is about bugs, no features should be assigned to the current release
|
||||
after first `-rc`. Supreme Committee is free to adjust priorities
|
||||
appropriately.
|
||||
|
||||
## Component version
|
||||
|
||||
Qubes release is defined as specific versions of components, which are
|
||||
developed more or less separately. Their versions are composed of major and
|
||||
minor version of target Qubes OS release followed by third component which is
|
||||
just incremented. There is no apparent indication that given version is stable
|
||||
or not.
|
||||
|
||||
There are some non-essential components like `qubes-apps-*` that are shared
|
||||
between releases. Their versions indicate oldest qubes-release that is
|
||||
supported. We try hard to support multiple releases by one branch to ease code
|
||||
maintenance.
|
||||
|
||||
Different Qubes releases remixes may comprise of different components and
|
||||
version are not guaranteed to be monotonic between releases. We may decide that
|
||||
for newer release some component should be downgraded. There is no guarantee
|
||||
that arbitrary combination of different versions of random components will
|
||||
yield usable (or even install-able) compilation.
|
||||
|
||||
## Git tags and branches
|
||||
|
||||
We mark each component version in the repository by tag containing
|
||||
`v<version>`. Likewise, each Qubes OS release is marked by `R<release>` tag.
|
||||
|
||||
At the release of some release we create branches named like `release2`. Only
|
||||
bug fixes and compatible improvements are backported to these branches. These
|
||||
branches should compile. All new development is done in `main` branch. This
|
||||
branch is totally unsupported and may not even compile depending on maintainer
|
||||
of repository.
|
||||
|
||||
All version and release tags should be made and signed by someone from ITL
|
||||
staff. Public keys are included in `qubes-builder` and available at
|
||||
<https://keys.qubes-os.org/keys/>.
|
||||
|
||||
## 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.
|
||||
107
developer/releases/version-scheme.rst
Normal file
107
developer/releases/version-scheme.rst
Normal file
|
|
@ -0,0 +1,107 @@
|
|||
==============
|
||||
Version scheme
|
||||
==============
|
||||
|
||||
|
||||
The Qubes OS Project uses the `semantic versioning <https://semver.org/>`__ standard. Version numbers are written as ``<major>.<minor>.<patch>``. When ``<patch>`` is omitted (e.g., ``4.1``), it is usually either because ``<patch>`` is zero (as in ``4.1.0``) or because we are referring to a specific minor release irrespective of any particular patch release within it. Similarly, the major release number alone (e.g., ``R4``) is sometimes used to refer to an entire release series inclusive of all minor and patch releases within it.
|
||||
|
||||
In general, patch releases are for backward-compatible bug fixes, minor releases are for backward-compatible enhancements and new features, and major release are for any backward-incompatible changes. This means that, in general, one should *not* try to introduce features or enhancements in patch releases or any backward-incompatible changes in patch or minor releases. (Templates are a notable exception, as upstream OSes almost always have their own release schedules.) Bug fixes are allowed in all releases, and backward-compatible changes are allowed in all major and minor releases.
|
||||
|
||||
Qubes OS minor releases generally include new features, new templates, and occasionally new defaults, but they are still backward-compatible in the sense that qubes and features that worked in the previous release still function, though the UI may be different in some cases. In general, deprecated features are removed only in major releases, and in-place upgrades between major versions are not guaranteed.
|
||||
|
||||
Following standard practice, **version** refers to any build that has been assigned a version name or number, e.g., ``3.2-rc2``, ``4.0.4``, ``4.1-beta1``. By contrast, **release** refers to any version that is intended for consumption by the general userbase. For example, ``4.0.4`` was both a **version** and a **release**, since it was stable and intended for general public use, while ``4.1-beta1`` was a **version** but *not* a **release**, since it was not stable and was intended only for :doc:`testing </user/downloading-installing-upgrading/testing>`. All releases are versions, but not all versions are releases.
|
||||
|
||||
The letter **R**, as in ``R4.1``, stands for **release**. The abbreviation **RC**, as in ``3.2-rc2``, stands for **release candidate**.
|
||||
|
||||
Qubes distributions and products
|
||||
--------------------------------
|
||||
|
||||
|
||||
We intend to make it easy to make a remix of Qubes, targeting another hypervisor or isolation provider. We may also create commercial products intended for specific circumstances. There is one distinguished distribution called **Qubes OS**. All source code for it is available for download under a :doc:`free and open-source license </developer/code/license>` and is openly developed on `GitHub <https://github.com/QubesOS>`__ and our :doc:`mailing lists </introduction/support>`. The rest of this document discusses Qubes OS. Another remix may have its own version series.
|
||||
|
||||
Release versioning
|
||||
------------------
|
||||
|
||||
|
||||
Qubes OS as a whole is released from time to time. When preparing a new release, we decide on the ``<major>.<minor>`` numbers (e.g., ``3.0``, which is short for ``3.0.0``). We then publish the first release candidate, e.g., ``3.0.0-rc1``. When we feel that enough progress has been made, we’ll release ``3.0.0-rc2`` and so on. All these versions (which are not yet releases) are considered unstable and are not intended for production use. You are welcome to :doc:`help us test </user/downloading-installing-upgrading/testing>` these versions.
|
||||
|
||||
When enough progress has been made, we announce the first stable release, e.g. ``3.0.0``. This is not only a version but an actual release. It is considered stable, and we commit to supporting it according to our :doc:`support schedule </user/downloading-installing-upgrading/supported-releases>`. Core components are branched at this moment, and bug fixes are backported from the main branch. Please see :doc:`help, support, mailing lists, and forum </introduction/support>` for places to ask questions about stable releases. No major features or interface incompatibilities are to be included in this release. We release bug fixes as patch releases (``3.0.1``, ``3.0.2``, and so on), while backward-compatible enhancements and new features are introduced in the next minor release (e.g., ``3.1``). Any backward-incompatible changes are introduced in the next major release (e.g., ``4.0``).
|
||||
|
||||
Please see :doc:`issue tracking </introduction/issue-tracking>` for information about how releases are handled in the issue tracker.
|
||||
|
||||
Release schedule
|
||||
----------------
|
||||
|
||||
|
||||
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.
|
||||
|
||||
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
|
||||
:align: center
|
||||
:header-rows: 1
|
||||
|
||||
* - Stage
|
||||
- Duration
|
||||
* - initial testing
|
||||
- two weeks
|
||||
* - bug fixing
|
||||
- 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.
|
||||
|
||||
|Release cycle|
|
||||
|
||||
Bug priorities
|
||||
--------------
|
||||
|
||||
|
||||
When deciding whether the current release candidate is the final one, the Committee takes bug :ref:`priorities <introduction/issue-tracking:priority>` into consideration. The meaning of them is as follows:
|
||||
|
||||
- ``blocker`` — when any such bug is present in the current release candidate, it can’t be considered final release. Bugs with this priority must be fixed before the next release candidate, even if that means delaying its release (which should be considered only last resort option).
|
||||
|
||||
- ``critical`` — when any such bug is present in the current release candidate, it can’t be considered final release. But such bugs are not qualified to delay next release candidate release.
|
||||
|
||||
- ``major`` — existence of such bugs do not strictly prevent the current release candidate be considered final (but of course we should try hard to not have them there). Fixing bugs of this priority can be delayed and qualified as updates to the final stable release.
|
||||
|
||||
- ``default`` and ``minor`` — existence of such bugs do not prevent the current release candidate be considered final. Fixing such bugs can be delayed to the next Qubes OS release. Eventually such fixes might be backported as an update to the stable release(s). (``default`` should really be assigned a more specific priority, but in practice there are too many issues and not enough time, so ``default`` ends up staying on many issues.)
|
||||
|
||||
|
||||
|
||||
All above is about bugs, no features should be assigned to the current release after first ``-rc``. Supreme Committee is free to adjust priorities appropriately.
|
||||
|
||||
Component version
|
||||
-----------------
|
||||
|
||||
|
||||
Qubes release is defined as specific versions of components, which are developed more or less separately. Their versions are composed of major and minor version of target Qubes OS release followed by third component which is just incremented. There is no apparent indication that given version is stable or not.
|
||||
|
||||
There are some non-essential components like ``qubes-apps-*`` that are shared between releases. Their versions indicate oldest qubes-release that is supported. We try hard to support multiple releases by one branch to ease code maintenance.
|
||||
|
||||
Different Qubes releases remixes may comprise of different components and version are not guaranteed to be monotonic between releases. We may decide that for newer release some component should be downgraded. There is no guarantee that arbitrary combination of different versions of random components will yield usable (or even install-able) compilation.
|
||||
|
||||
Git tags and branches
|
||||
---------------------
|
||||
|
||||
|
||||
We mark each component version in the repository by tag containing ``v<version>``. Likewise, each Qubes OS release is marked by ``R<release>`` tag.
|
||||
|
||||
At the release of some release we create branches named like ``release2``. Only bug fixes and compatible improvements are backported to these branches. These branches should compile. All new development is done in ``main`` branch. This branch is totally unsupported and may not even compile depending on maintainer of repository.
|
||||
|
||||
All version and release tags should be made and signed by someone from ITL staff. Public keys are included in ``qubes-builder`` and available at https://keys.qubes-os.org/keys/.
|
||||
|
||||
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
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue