Wiki » History » Revision 10
« Previous |
Revision 10/18
(diff)
| Next »
ph03nix, 2024-10-21 12:28
Wiki¶
QE-C backlog for Non-PublicCloud tasks (Containers and Images). The PublicCloud backlog is at https://progress.opensuse.org/projects/public_cloud/.
The keywords must
, must not
, should
, should not
and may
follow RFC2119.
Containers and Images backlog¶
The overall scope can be defined by the following domains and their associated tags:
Name | Description | Domain tag |
---|---|---|
Container | Tickets that affect testing of the container engines (podman , docker , ...) and container images (BCI, SAC, Base images, RMT, ...) |
container |
MinimalVM images | MinimalVM (former JeOS) testing | MinimalVM |
SLE-Micro images | Testing of SLE-Micro images. This should not include container engines on SLE-Micro. | slem |
WSL images | Testing of Windows Subsystem for Linux | wsl |
Every ticket must contain exactly one of those domain tags. If not applicable the tag to-be-refined
must be used.
Housekeeping¶
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.
- Squad members should take the highest priority tickets marked as Workable first.
- Tickets regarding fixing test issues should always have high priority.
- Only the PO should set tickets from New to Workable .
- Tickets for fixing test issues must be set immediately to Workable and the priority to high.
- New non-fixing tickets must be set to New and must contain the domain tags above or
to-be-refined
if unknown. - If tickets are unclear, they must be tagged
to-be-refined
and set then to New . Every squad member is allowed to set ticket from Workable to New. - 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.
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.
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.
Updated by ph03nix 3 months ago · 10 revisions