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 is defined by the following domains and their associated tags:

A domain tag is a normal ticket tag. Every ticket must contain exactly one of the above defined domain tags.
If not applicable (or unknown) the tag to-be-refined must be used. The to-be-refined tag can be used together with domain tags.

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.

1. Squad members should take the highest priority tickets marked as Workable first.
2. Tickets regarding fixing test issues should always have high priority.
3. Only the PO should set tickets from New to Workable and only the PO should adjust ticket priorities.
4. Tickets for fixing test issues must be set immediately to Workable and the priority to high.
5. New non-fixing tickets must be set to New and must contain the domain tags above or to-be-refined if unknown. The priority should be normal .
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.
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.

Lower number rules have precedence. This means e.g. new tickets for fixing test issues are set to Workable and priority high, because rule 4 from the list above has higher precedence than rule 5.

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.