From 7c7e9380eec1e1b84a1d1bbff2c177e8112bf47a Mon Sep 17 00:00:00 2001 From: YAMAMOTO Takashi Date: Fri, 27 Jul 2018 18:06:06 +0900 Subject: [PATCH] Bug deputy routines for dummies I always keep forgetting what to do and it's a little time consuming to re-read the previous sections at the beginning of every my weeks. Hopefully, this can be useful for others too. Change-Id: Ic7543d276f7cfa2ee70f6b97340d70db5cc12d10 --- doc/source/contributor/policies/bugs.rst | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/doc/source/contributor/policies/bugs.rst b/doc/source/contributor/policies/bugs.rst index 1d3e558da12..8f5bc38312c 100644 --- a/doc/source/contributor/policies/bugs.rst +++ b/doc/source/contributor/policies/bugs.rst @@ -122,6 +122,25 @@ steps you will need to follow in order to be prepared. can be present to discuss them. +Bug Deputy routines in your week +-------------------------------- + +* Scan 'New' bugs to triage. + If it doesn't have enough info to triage, ask more info and + mark it 'Incomplete'. + If you could confirm it by yourself, mark it 'Confirmed'. + Otherwise, find someone familiar with the topic and ask his/her help. + +* Scan 'Incomplete' bugs to see if it got more info. + If it was, make it back to 'New'. + +* Repeat the above routines for bugs filed in your week at least. + If you can, do the same for older bugs. + +* Take a note of bugs you processed. + At the end of your week, post a report on openstack-dev mailing list. + + Plugin and Driver Repositories ------------------------------