From 588eca1e182137cd663f7bc364e0723cc24a4ae5 Mon Sep 17 00:00:00 2001 From: Anoop C S Date: Tue, 16 Feb 2016 20:15:34 +0530 Subject: [PATCH] Add closing procedure for mainline BZ to Bug-report-Life-Cycle.md Signed-off-by: Anoop C S --- Contributors-Guide/Bug-report-Life-Cycle.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Contributors-Guide/Bug-report-Life-Cycle.md b/Contributors-Guide/Bug-report-Life-Cycle.md index 3749bd6..27a3956 100644 --- a/Contributors-Guide/Bug-report-Life-Cycle.md +++ b/Contributors-Guide/Bug-report-Life-Cycle.md @@ -33,9 +33,11 @@ This page describes the life of a bug report. failed. - When a report has been solved it is given **CLOSED** status. This can mean: - - **CLOSED/CURRENTRELEASE** when a code change that fixes the - reported problem has been merged in - [Gerrit](http://review.gluster.org). + - **CLOSED/NEXTRELEASE** when backport of the code change that + fixes the reported mainline problem has been merged. + - **CLOSED/CURRENTRELEASE** when the code change that fixes the + reported bug has been merged in the corresponding release-branch + and a version is released with the fix. - **CLOSED/WONTFIX** when the reported problem or suggestion is valid, but any fix of the reported problem or implementation of the suggestion would be barred from approval by the project's