[Gluster-Maintainers] Bug state change proposal based on the conversation on bz 1630368

[Kaleb S. KEITHLEY]

On 11/5/18 7:01 AM, Pranith Kumar Karampuri wrote:
> hi,
>     When we create a bz on master and clone it to the next release(In my
> case it was release-5.0), after that release happens can we close the bz
> on master with CLOSED NEXTRELEASE?
> 
> Please Check the comments
> https://bugzilla.redhat.com/show_bug.cgi?id=1630368#c5 till
> https://bugzilla.redhat.com/show_bug.cgi?id=1630368#c8
> 

Perhaps there are some implicit steps that should be stated explicitly?

Starting with a BZ¹ on master:
1) post fix on master
2) change BZ¹ to POST (automatic)
3) merge fix on master
4) change BZ¹ to MODIFIED (is this automatic too?)
5) clone BZ¹ to BZ²(release-5)
6) optional: close master BZ¹ as CLOSED/NEXTRELEASE, Fixed In: 6
7) post fix on release-5
8) change BZ² to POST (automatic)
9) merge fix on release-5
10) change BZ² to MODIFIED, Fixed In: 5.x
11) tag 5.x
12) change BZ² to ONQA or CLOSED/CURRENTRELEASE
#if fix is needed on release-4.1 branch
 13) clone BZ¹ to BZ³(release-4.1)
 14) post fix on release-4.1
 15) change BZ³ to POST (automatic)
 16) merge fix on release-4.1
 17) change BZ³ to MODIFIED, Fixed In: 4.1.x
 18) tag 4.1.x
 19) change BZ³ to ONQA or CLOSED/CURRENTRELEASE
#endif
20) over time any ONQA BZs can be changed to CLOSED/CURRENTRELEASE by
the maintainer based on feedback (or lack thereof) from the community.
21) at EOL any remaining ONQA BZs are changed to CLOSED/CURRENTRELEASE


-- 

Kaleb