Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-10-01 01:25:40 -04:00
Code Issues Packages Projects Releases Wiki Activity
4ff7430960
qubes-doc/user/downloading-installing-upgrading/testing.md

65 lines
4.0 KiB
Markdown
Raw Normal View History

Create page about testing new releases and updates
2017-03-20 21:33:08 -04:00
---
Add lang + ref tags to frontmatter Those are fields used by the language switcher to correlate pages across different languages, even if they have different names/paths/titles. They are generated with the prepare_for_translation.py script.
2021-03-13 13:06:18 -05:00
lang: en
Create page about testing new releases and updates
2017-03-20 21:33:08 -04:00
layout: doc
Remove all instances of `permalink:` in YAML frontmatter Converts existing permalink paths into redirect_from entries. QubesOS/qubes-issues#6701
2021-06-16 01:33:51 -04:00
redirect_from:
- /doc/testing/
Add lang + ref tags to frontmatter Those are fields used by the language switcher to correlate pages across different languages, even if they have different names/paths/titles. They are generated with the prepare_for_translation.py script.
2021-03-13 13:06:18 -05:00
ref: 147
Revert "Remove instances of `title:` from YAML headers" This reverts commit 24e6a8a616bfba80534d5d700b2f6b02745561fe. https://github.com/QubesOS/qubes-issues/issues/6701#issuecomment-862060759
2021-06-16 02:19:45 -04:00
title: Testing new releases and updates
Create page about testing new releases and updates
2017-03-20 21:33:08 -04:00
---
Refactor links in order to obey the new convention rule
2021-04-10 18:09:05 -04:00
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.
Update testing page - Convert text warning into alert; add text - Minor language improvements and fixes - Normalize heading capitalization
2021-06-12 22:29:17 -04:00
<div class="alert alert-danger" role="alert">
<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.
Create page about testing new releases and updates
2017-03-20 21:33:08 -04:00
Releases
--------
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
Create page about testing new releases and updates
2017-03-20 21:33:08 -04:00
How to test upcoming Qubes OS releases:
Refactor links in order to obey the new convention rule
2021-04-10 18:09:05 -04:00
* Use [qubes-builder](/doc/qubes-builder/) to build the latest release.
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
* Test the latest release candidate (RC), if any is currently available.
* (No support) Experiment with devel alpha ISOs found from time to time at [Qubes OpenQA](https://openqa.qubes-os.org/).
Create page about testing new releases and updates
2017-03-20 21:33:08 -04:00
Update testing page - Convert text warning into alert; add text - Minor language improvements and fixes - Normalize heading capitalization
2021-06-12 22:29:17 -04:00
Please make sure to [report any bugs you encounter](/doc/reporting-bugs/).
Refactor links in order to obey the new convention rule
2021-04-10 18:09:05 -04:00
See [Version Scheme](/doc/version-scheme/) for details about release versions and schedules.
See [Release Checklist](/doc/releases/todo/) for details about the RC process.
Create page about testing new releases and updates
2017-03-20 21:33:08 -04:00
Updates
-------
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
Create page about testing new releases and updates
2017-03-20 21:33:08 -04:00
How to test updates:
Refactor links in order to obey the new convention rule
2021-04-10 18:09:05 -04:00
* Enable [dom0 testing repositories](/doc/software-update-dom0/#testing-repositories).
* Enable [TemplateVM testing repositories](/doc/software-update-domu/#testing-repositories).
Create page about testing new releases and updates
2017-03-20 21:33:08 -04:00
Document testing practices (QubesOS/qubes-issues#4846)
2019-08-26 18:57:50 -04:00
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.
The update remains in `security-testing` or `current-testing` for a minimum of one week.
Clarify exception for critical security updates
2019-08-26 19:00:47 -04:00
On occasion, an exception is made for a particularly critical security update, 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`.
Update testing page - Convert text warning into alert; add text - Minor language improvements and fixes - Normalize heading capitalization
2021-06-12 22:29:17 -04:00
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.
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.
Document testing practices (QubesOS/qubes-issues#4846)
2019-08-26 18:57:50 -04:00
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`.
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.
Update testing page - Convert text warning into alert; add text - Minor language improvements and fixes - Normalize heading capitalization
2021-06-12 22:29:17 -04:00
Providing feedback
Create page about testing new releases and updates
2017-03-20 21:33:08 -04:00
------------------
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
Update testing page - Convert text warning into alert; add text - Minor language improvements and fixes - Normalize heading capitalization
2021-06-12 22:29:17 -04:00
Since the whole point of testing software is to discover and fix bugs, your feedback is an essential part of this process.
Create page about testing new releases and updates
2017-03-20 21:33:08 -04:00
Refactor links in order to obey the new convention rule
2021-04-10 18:09:05 -04:00
We use an [automated build process](https://github.com/QubesOS/qubes-infrastructure/blob/master/README.md).
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.
Create page about testing new releases and updates
2017-03-20 21:33:08 -04:00
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.
Refactor links in order to obey the new convention rule
2021-04-10 18:09:05 -04:00
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).
Reference in New Issue Copy Permalink