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.
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
Process: support tiers for hardware for Zephyr v3.3 and later #38566
Comments
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
related discussion: |
Process WG:
|
Proposal for board tier names and descriptions:
Minutes: Support tiers:
Test selection:
|
Process WG:
|
Process WG:
|
Process WG:
|
Process WG:
|
Process WG:
|
Process WG:
|
We've had TSC approval for this in principle for a while, and have now moved the implementation work to the testing WG's domain |
This issue covers a process discussion for introducing support tiers for boards with upstream Zephyr project support.
The goal of this issue is to define a high level process for defining the support level for different Zephyr boards. This will aid users in knowing which platforms are well tested and debugged. For a related release criteria issue, see #46759.
Proposal for board tier names and descriptions:
This will also affect the release criteria for future versions of zephyr:
Once the high level process is defined, the goal is for the testing working group to manage the details with input from interested stakeholders.
Previous discussion:
https://docs.google.com/document/d/1LOhgronKx3TxUypYLy9nex0_3UC58FMMjbXV4wbiuiE/edit#
The text was updated successfully, but these errors were encountered: