Skip to content

docs: align to dasharo naming convention v2 #1177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs: align to dasharo naming convention v2 #1177

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/dasharo-naming-convention.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Available options:

- `platform`: Indicates the target platform for the package. Platform is
mandatory in public names. Platform name should follow [supported hardware
list](/variants/overview).
list](variants/overview.md).
- `edition`: Community | Pro | Enterprise (edition codes: DCP, DPP, DEP)

- `release`: Rapid | Assured | LTS. Defines QA scope and support cadence. Codes
Expand Down
19 changes: 0 additions & 19 deletions docs/osf-trivia-list/dasharo.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -147,25 +147,6 @@ There is also a libre, POWER9-based server/workstation Talos II by Raptor
Computing Systems, which also do not use any binary blobs, however it is more
expensive than x86 platforms.

## What is Dasharo non-LTS release?

Dasharo non-LTS release is a release that is validated with a reduced set of
tests. The non-LTS name is adopted from distributions which mark their Long
Term Support (LTS) releases as extensively validated/higher quality assurance. For
example see [Ubuntu documentation](https://ubuntu.com/about/release-cycle).

The reduced set of tests includes the test cases marked with
`minimal-regression` tag in the [OSFV
repository](https://github.com/Dasharo/open-source-firmware-validation/blob/develop/docs/adding-and-naming-test-cases.md#test-workflow-tag-guidelines).
Tagging the tests allow to run a subset of tests with given tag. Example
command, how to run `minimal-regression` tests can be found
[here](https://github.com/Dasharo/open-source-firmware-validation/blob/develop/README.md#running-regression-tests-with-additional-arguments).

Dasharo releases which are not marked as non-LTS undergo a full set of
regression tests applicable for a platform. To check results of the tests or
the test scope for given release, visit [OSFV results
repository](https://github.com/Dasharo/osfv-results).

## Why Dasharo?

### Open-source firmware ecosystem problems
Expand Down
4 changes: 2 additions & 2 deletions docs/variants/msi_z690/releases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,8 +25,8 @@ For details about our release process please read

## v1.1.5 - 2025-09-18

This is a [non-LTS
release](../../osf-trivia-list/dasharo.md#what-is-dasharo-non-lts-release) and
This is a [Rapid
release](../../dasharo-naming-convention.md) and
has a reduced scope of tests.

Test results for this release can be found
Expand Down
4 changes: 2 additions & 2 deletions docs/variants/msi_z790/releases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,8 +25,8 @@ recommend seeing our [FAQ](../../unified/msi/faq.md).

## v0.9.3 - 2025-09-18

This is a [non-LTS
release](../../osf-trivia-list/dasharo.md#what-is-dasharo-non-lts-release) and
This is a [Rapid
release](../../dasharo-naming-convention.md) and
has a reduced scope of tests.

Test results for this release can be found
Expand Down