[Gluster-devel] question about how to handle bugs filed against End-Of-Life versions of glusterfs

[Kaleb S. KEITHLEY]

Hi,

A question was raised during Tuesday's (2015-09-15) Gluster Bug Triage
meeting[1], and discussed today (2015-09-16) at the Gluster Community
meeting[2] about how to handle currently open bugs and new bugs filed
against GlusterFS versions which have reached end-of-life (EOL).

As an example, Fedora simply closes any remaining open bugs when the
version reaches EOL. It's incumbent on the person who filed the bug to
reopen it if it still exists in newer versions.

Option A is: create a new set of 'umbrella' Versions, e.g.
3.4-end-of-life, 3.3-end-of-life, etc.; _reassign_ all bugs filed
against 3.4.x to 3.4.x-end-of-life; then delete the 3.4.x Versions from
bugzilla. Any new bugs filed against, e.g., any 3.4.x version are
assigned to, 3.4-end-of-life.

Option B is: create a new set of 'umbrella' Versions, e.g.
3.4-end-of-life, 3.3-end-of-life, etc.; _close_ all bugs filed against
3.4.x; then delete the 3.4.x Versions from bugzilla. Any new bugs filed
against, e.g., any 3.4.x version are assigned to, 3.4-end-of-life.

The main difference is whether existing bugs are reassigned or simply
closed. In either case if a new bug is filed against an EOL version then
during bug triage the bug will be checked to see if it still exists in
newer versions and reassigned to the later version, or closed as
appropriate.

You may reply to this email — Reply-to: is set to
mailto:gluster-devel at gluster.org — to register your opinion.

Thanks,


[1]
http://meetbot.fedoraproject.org/gluster-meeting/2015-09-15/gluster-meeting.2015-09-15-12.02.log.html
[2]
http://meetbot.fedoraproject.org/gluster-meeting/2015-09-16/gluster-meeting.2015-09-16-12.01.log.html

-- 

Kaleb