Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-07-29 01:28:59 -04:00
Code Issues Projects Releases Packages Wiki Activity

QA rst conversion releases section: replace master with main in 1 file, archive link from a currently dead one, typo fix

Browse source
This commit is contained in:
qubedmaiska 2025-02-14 17:51:17 -05:00
parent 8fb701ea79
commit d6925e063d
No known key found for this signature in database
GPG key ID: 204BCE0FD52C0501
3 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
developer/releases/2_0/release-notes.md
View file

@ -68,7 +68,7 @@ Note: if the user has custom Template VMs (i.e. other than the default template,
#### From Qubes R1 to R2 beta1 #### 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/). 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 #### From Qubes R1 or R2 Beta 1 to R2 beta2

2
developer/releases/4_0/release-notes.md
View file

@ -9,7 +9,7 @@ title: Qubes R4.0 release notes
New features since 3.2 New features since 3.2
---------------------- ----------------------
* Core management scripts rewrite with better structure and extensibility, [API documentation](https://dev.qubes-os.org/projects/qubes-core-admin/en/latest/) * Core management scripts rewrite with better structure and extensibility, [API documentation](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 * [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 * 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 * Renaming VM directly is prohibited, there is GUI to clone under new name and remove old VM

4
developer/releases/version-scheme.md
View file

@ -71,7 +71,7 @@ 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 `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 stable, and we commit to supporting it according to our [support
schedule](/doc/supported-releases/). Core components are branched at this schedule](/doc/supported-releases/). Core components are branched at this
moment, and bug fixes are backported from the master branch. Please see [help, 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 support, mailing lists, and forum](/support/) for places to ask questions about
stable releases. No major features or interface incompatibilities are to be 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`, included in this release. We release bug fixes as patch releases (`3.0.1`,
@ -173,7 +173,7 @@ We mark each component version in the repository by tag containing
At the release of some release we create branches named like `release2`. Only At the release of some release we create branches named like `release2`. Only
bug fixes and compatible improvements are backported to these branches. These bug fixes and compatible improvements are backported to these branches. These
branches should compile. All new development is done in `master` branch. This branches should compile. All new development is done in `main` branch. This
branch is totally unsupported and may not even compile depending on maintainer branch is totally unsupported and may not even compile depending on maintainer
of repository. of repository.