mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-10-01 01:25:40 -04:00
Update "Testing New Releases and Updates"
- Convert alert into text warning (Now that every advanced page has the same sticky alert at the top, it looks odd to have similar alerts above and below the h1 heading.) - Update heading syntax - Wrap text
This commit is contained in:
Andrew David Wong
parent
f490482273
commit
6a88601739
@ -7,58 +7,79 @@ advanced: true
|
|||||||
title: Testing New Releases and Updates
|
title: Testing New Releases and Updates
|
||||||
---
|
---
|
||||||
|
|
||||||
|
Testing new Qubes OS releases and updates is one of the most helpful ways in
|
||||||
|
which you can [contribute](/doc/contributing/) to the Qubes OS Project. There
|
||||||
|
are several different types of testing, which we'll cover below.
|
||||||
|
|
||||||
Testing new Qubes OS releases and updates is one of the most helpful ways in which you can [contribute](/doc/contributing/) to the Qubes OS Project.
|
**Warning:** Software testing is intended for advanced users and developers.
|
||||||
|
You should only attempt to do this if you know what you're doing. Never rely on
|
||||||
|
code that is in testing for critical work!
|
||||||
|
|
||||||
<div class="alert alert-danger" role="alert">
|
## Releases
|
||||||
<i class="fa fa-exclamation-triangle"></i>
|
|
||||||
<b>Warning:</b> Software testing is intended for advanced users and developers. You should only attempt to do this if you know what you're doing. Never rely on code that is in testing for critical work!
|
|
||||||
</div>
|
|
||||||
|
|
||||||
There are several different types of testing, which we'll cover below.
|
|
||||||
|
|
||||||
Releases
|
|
||||||
--------
|
|
||||||
|
|
||||||
How to test upcoming Qubes OS releases:
|
How to test upcoming Qubes OS releases:
|
||||||
|
|
||||||
* Use [qubes-builder](/doc/qubes-builder/) to build the latest release.
|
* Use [qubes-builder](/doc/qubes-builder/) to build the latest release.
|
||||||
* Test the latest release candidate (RC), if any is currently available.
|
* Test the latest release candidate (RC), if one is currently available.
|
||||||
* (No support) Experiment with devel alpha ISOs found from time to time at [Qubes OpenQA](https://openqa.qubes-os.org/).
|
* (No support) Experiment with devel alpha ISOs found from time to time at
|
||||||
|
[Qubes OpenQA](https://openqa.qubes-os.org/).
|
||||||
|
|
||||||
Please make sure to [report any bugs you encounter](/doc/reporting-bugs/).
|
Please make sure to [report any bugs you encounter](/doc/reporting-bugs/).
|
||||||
|
|
||||||
See [Version Scheme](/doc/version-scheme/) for details about release versions and schedules.
|
See [Version Scheme](/doc/version-scheme/) for details about release versions
|
||||||
See [Release Checklist](/doc/releases/todo/) for details about the RC process.
|
and schedules. See [Release Checklist](/doc/releases/todo/) for details about
|
||||||
|
the RC process.
|
||||||
|
|
||||||
Updates
|
## Updates
|
||||||
-------
|
|
||||||
|
|
||||||
How to test updates:
|
How to test updates:
|
||||||
|
|
||||||
* Enable [dom0 testing repositories](/doc/how-to-install-software-in-dom0/#testing-repositories).
|
* Enable [dom0 testing
|
||||||
* Enable [template testing repositories](/doc/how-to-install-software/#testing-repositories).
|
repositories](/doc/how-to-install-software-in-dom0/#testing-repositories).
|
||||||
|
* Enable [template testing
|
||||||
|
repositories](/doc/how-to-install-software/#testing-repositories).
|
||||||
|
|
||||||
Every new update is first uploaded to the `security-testing` repository if it is a security update or `current-testing` if it is a normal update.
|
Every new update is first uploaded to the `security-testing` repository if it
|
||||||
The update remains in `security-testing` or `current-testing` for a minimum of one week.
|
is a security update or `current-testing` if it is a normal update. The update
|
||||||
On occasion, an exception is made for a particularly critical security update, which is immediately pushed to the `current` stable repository.
|
remains in `security-testing` or `current-testing` for a minimum of one week.
|
||||||
In general, however, security updates remain in `security-testing` for two weeks before migrating to `current`.
|
On occasion, an exception is made for a particularly critical security update,
|
||||||
Normal updates generally remain in `current-testing` until they have been sufficiently tested by the community, which can last weeks or even months, depending on the amount of feedback received (see [Providing feedback](#providing-feedback)).
|
which is immediately pushed to the `current` stable repository. In general,
|
||||||
|
however, security updates remain in `security-testing` for two weeks before
|
||||||
|
migrating to `current`. Normal updates generally remain in `current-testing`
|
||||||
|
until they have been sufficiently tested by the community, which can last weeks
|
||||||
|
or even months, depending on the amount of feedback received (see [Providing
|
||||||
|
feedback](#providing-feedback)).
|
||||||
|
|
||||||
"Sufficient testing" is, in practice, a fluid term that is up the developers' judgment.
|
"Sufficient testing" is, in practice, a fluid term that is up the developers'
|
||||||
In general, it means either that no negative feedback and at least one piece of positive feedback has been received or that the package has been in `current-testing` for long enough, depending on the component and the complexity of the changes.
|
judgment. In general, it means either that no negative feedback and at least
|
||||||
|
one piece of positive feedback has been received or that the package has been
|
||||||
|
in `current-testing` for long enough, depending on the component and the
|
||||||
|
complexity of the changes.
|
||||||
|
|
||||||
A limitation of the current testing setup is that it is only possible to migrate the *most recent version* of a package from `current-testing` to `current`.
|
A limitation of the current testing setup is that it is only possible to
|
||||||
This means that, if a newer version of a package is uploaded to `current-testing`, it will no longer be possible to migrate any older versions of that same package from `current-testing` to `current`, even if one of those older versions has been deemed stable enough.
|
migrate the *most recent version* of a package from `current-testing` to
|
||||||
While this limitation can be inconvenient, the benefits outweigh the costs, since it greatly simplifies the testing and reporting process.
|
`current`. This means that, if a newer version of a package is uploaded to
|
||||||
|
`current-testing`, it will no longer be possible to migrate any older versions
|
||||||
|
of that same package from `current-testing` to `current`, even if one of those
|
||||||
|
older versions has been deemed stable enough. While this limitation can be
|
||||||
|
inconvenient, the benefits outweigh the costs, since it greatly simplifies the
|
||||||
|
testing and reporting process.
|
||||||
|
|
||||||
Providing feedback
|
## Providing feedback
|
||||||
------------------
|
|
||||||
|
|
||||||
Since the whole point of testing software is to discover and fix bugs, your feedback is an essential part of this process.
|
Since the whole point of testing software is to discover and fix bugs, your
|
||||||
|
feedback is an essential part of this process.
|
||||||
|
|
||||||
We use an [automated build process](https://github.com/QubesOS/qubes-infrastructure/blob/master/README.md).
|
We use an [automated build
|
||||||
For every package that is uploaded to a testing repository, a GitHub issue is created in the [updates-status](https://github.com/QubesOS/updates-status/issues) repository for tracking purposes.
|
process](https://github.com/QubesOS/qubes-infrastructure/blob/master/README.md).
|
||||||
We welcome any kind of feedback on any package in any testing repository.
|
For every package that is uploaded to a testing repository, a GitHub issue is
|
||||||
Even a simple <span class="fa fa-thumbs-up" title="Thumbs Up"></span> or <span class="fa fa-thumbs-down" title="Thumbs Down"></span> on the package's associated issue would help us to decide whether the package is ready to be migrated to a stable repository.
|
created in the
|
||||||
If you [report a bug](/doc/reporting-bugs/) in a package that is in a testing repository, please reference the appropriate issue in [updates-status](https://github.com/QubesOS/updates-status/issues).
|
[updates-status](https://github.com/QubesOS/updates-status/issues) repository
|
||||||
|
for tracking purposes. We welcome any kind of feedback on any package in any
|
||||||
|
testing repository. Even a simple <span class="fa fa-thumbs-up" title="Thumbs
|
||||||
|
Up"></span> or <span class="fa fa-thumbs-down" title="Thumbs Down"></span> on
|
||||||
|
the package's associated issue would help us to decide whether the package is
|
||||||
|
ready to be migrated to a stable repository. If you [report a
|
||||||
|
bug](/doc/reporting-bugs/) in a package that is in a testing repository, please
|
||||||
|
reference the appropriate issue in
|
||||||
|
[updates-status](https://github.com/QubesOS/updates-status/issues).
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user