Hi Yuri, Here is how I understand the proposed use case for the Affected Versions: and ceph-qa-suite: fields in http://tracker.ceph.com/
When the issue is created: * Select Affected Versions: to match the Ceph version of the bug report * Select the ceph-qa-suite where the bug can be reproduced or where the feature will be tested When a job from a suite S fails * If the analysis of the job failure points to an existing issue * If closed, the issue is re-opened * The Affected Versions: is modified to include the Ceph version from the job failure * The ceph-qa-suite is modified to include the suite the job belongs to When preparing a release for Ceph version V * To check if the rados suite has no pending bug, query the issues that are open and Affected Versions: matches V and ceph-qa-suite matches rados * To check if there are no pending bug, query the issues that are open and Affected Versions: matches V Am I missing something ? Cheers -- Loïc Dachary, Artisan Logiciel Libre
signature.asc
Description: OpenPGP digital signature
