[Gluster-devel] Update on setting and maintaining a trackable status for bugs

[Niels de Vos]

On Fri, Jul 11, 2014 at 10:10:32PM +0200, Niels de Vos wrote:
> Hi all,
> 
> we (sub-maintainers and component owners) will be trying to enforce 
> a more trackable status of the various bugs that we have and get 
> reported. In order to get everyone on one line, we will follow 
> a documented life-cycle for the bugs:
> - http://www.gluster.org/community/documentation/index.php/Bug_report_life_cycle
> 
> The life-cycle will help developers and bug reporters understanding 
> where in the process a certain fix is. It makes it easier to find the 
> package versions that should solve the reported issues. With this, we 
> hope to get more verifications of fixes from the bug reporters and other 
> community users.
> 
> With help from some scripts, I have been checking and correcting the 
> status of many bugs this evening. Now, most¹ bugs that have:
> 
> 1. patches posted, should be in POST
> 2. have all their patches merged, should be in MODIFIED
> 3. have patches merged and a beta release contains those, ON_QA
> 4. where all patches have been included in a final release, CLOSED

The outstanding bugs have been corrected now too. There are only a few 
exceptions where I could make little sense of the status. I'll follow up 
on those with the assigned engineers and/or developers who sent a patch.

Some bugs have been moved from ON_QA or VERIFIED to MODIFIED. This only 
affects bugs that have patches filed against the master branch. There 
have been no alpha/beta releases (or tags in git) for glusterfs-3.6 yet, 
and therefor it was not possible to test those changes in a consistent 
way.

We should make sure to keep a difference between VERIFIED in a bug 
report, and Verified:+1 in Gerrit. The 1st is related to a published 
(alpha/beta) version of GlusterFS, the 2nd informs the code reviewers 
and maintainers that the posted patch works as intended.

> So, don't be surprised to see many bug changes.

If you have questions about a particular status change of a bug, let me 
know and I'll happily explain my reasoning.

Cheers,
Niels