Bug triage and software reviews¶

The OpenStack Charms project operates two rotas for managing bug triage and software reviews: one associated with triage of new bugs and the other related to the review of software changes in Gerrit.

Community members are encouraged to sign up to both rotas. Please coordinate with us!

Bug tags¶

When triaging or filing bugs for OpenStack Charms projects, please use the following Launchpad tags:

openstack-upgrade - Issues upgrading the charm payload (OpenStack version), such as Train to Ussuri.
charm-upgrade - Issues upgrading the charm revision, such as cs:foo-100 to cs:foo-101 (not a payload or OpenStack version upgrade, not a series upgrade).
series-upgrade - Issues upgrading from one series to the next, i.e. Bionic to Focal.
ceph-upgrade - Issues upgrading the Ceph version (not charm upgrade).
scaleback - Issues removing a unit, shrinking a cluster, replacing a unit.
cold-start - Issues in recovering the charm payload functionality after a power event such as a reboot or shutdown.
cross-model - Issues with Cross-Model Relations.
unstable-test - Issues that result in automated tests producing false negatives or positives.

Rota schedules¶

People are assigned to the rotas using an alternating daily schedule. The names in the tables are Launchpad IDs.

Bug triage¶

For triaging new bugs across the OpenStack Charms.

Monday	Tuesday	Wednesday	Thursday	Friday
gnuoy	fnordahl	freyes	james-page	billy-olsen
aurelien-lourot	chris-icey	dmitriis	coreycb	alex-tinwood

Charm review¶

For reviewing all open changes and all reviewable items across the OpenStack Charms.

Monday	Tuesday	Wednesday	Thursday	Friday
freyes	james-page	fnordahl	billy-olsen	chris-icey
dmitriis	coreycb	alex-tinwood	gnuoy	aurelien-lourot

Filtering in Gerrit¶

Sophisticated filtering is possible in Gerrit. For instance, to find open changes to YAML files that have been in the queue for less than two months and do not have a value of ‘-1’ for the Workflow label: open changes to YAML files.

Abandonment policy¶

Charm reviews which are either blocked (> 12 weeks without comment and are blocked by a core reviewer with a -2 review) or failing (> 12 weeks without comment and failed tests the last time the review was checked) will be automatically marked as abandoned within Gerrit.

Abandoned reviews can always be restored in the event that work on a review resumes - reviews that are blocked by a -2 review will also need to be discussed with the core reviewer involved.

Any review marked as work in progress (Workflow -1) will be excluded from this policy.

Bug triage and software reviews