Wiki » History » Version 12
ph03nix, 2024-10-21 12:38
| 1 | 8 | ph03nix | # Wiki |
|---|---|---|---|
| 2 | |||
| 3 | 7 | ph03nix | QE-C backlog for Non-PublicCloud tasks (Containers and Images). The PublicCloud backlog is at https://progress.opensuse.org/projects/public_cloud/. |
| 4 | 1 | ph03nix | |
| 5 | 7 | ph03nix | The keywords `must`, `must not`, `should`, `should not` and `may` follow [RFC2119](https://www.rfc-editor.org/rfc/rfc2119). |
| 6 | 1 | ph03nix | |
| 7 | 7 | ph03nix | # Containers and Images backlog |
| 8 | |||
| 9 | The overall scope can be defined by the following domains and their associated tags: |
||
| 10 | |||
| 11 | |Name|Description|Domain tag| |
||
| 12 | 3 | ph03nix | |--|--|--| |
| 13 | 4 | ph03nix | |Container|Tickets that affect testing of the container engines (`podman`, `docker`, ...) and container images (BCI, SAC, Base images, RMT, ...) | `container` | |
| 14 | 3 | ph03nix | |MinimalVM images|MinimalVM (former JeOS) testing|`MinimalVM`| |
| 15 | 1 | ph03nix | |SLE-Micro images|Testing of SLE-Micro images. This should not include container engines on SLE-Micro.|`slem`| |
| 16 | |WSL images|Testing of Windows Subsystem for Linux|`wsl`| |
||
| 17 | 3 | ph03nix | |
| 18 | 11 | ph03nix | Every ticket must contain exactly one of those domain tags. If not applicable the tag `to-be-refined` must be used. The `to-be-refined` tag can be used together with domain tags. |
| 19 | 7 | ph03nix | |
| 20 | 1 | ph03nix | ## Housekeeping |
| 21 | |||
| 22 | 7 | ph03nix | We follow the rules of https://progress.opensuse.org/projects/openqav3/wiki/Wiki#ticket-workflow. In addition, the following rules are specific for this backlog. Lower number rules have precedence. |
| 23 | 1 | ph03nix | |
| 24 | 6 | ph03nix | 1. Squad members should take the highest priority tickets marked as *Workable* first. |
| 25 | 2. Tickets regarding fixing test issues should always have high priority. |
||
| 26 | 12 | ph03nix | 3. Only the PO should set tickets from *New* to *Workable* and only the PO should adjust ticket priorities. |
| 27 | 6 | ph03nix | 4. Tickets for fixing test issues must be set immediately to *Workable* and the priority to *high*. |
| 28 | 10 | ph03nix | 5. New non-fixing tickets must be set to *New* and must contain the domain tags above or `to-be-refined` if unknown. |
| 29 | 11 | ph03nix | 6. If tickets are unclear, they must be tagged `to-be-refined` and set to *New* . Every squad member is allowed to set ticket from *Workable* to *New*. |
| 30 | 6 | ph03nix | 7. Tickets should always be the smallest actionable item. If a task can be split into two tickets, it should be. Larger topics should be organized via epics/sagas. |
| 31 | |||
| 32 | Good tickets should provide sufficient context, i.e. a description of why this is required or at least links to relevant sources. If you believe a ticket is incomplete, follow rule 6 and ping the owner of the ticket. |