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

[Pat Riehecky]

On 09/16/2015 08:05 AM, Kaleb S. KEITHLEY wrote:
> 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
>

I'd go with Option B (close the bugs), so long as it is possible to 
either (a) re-open or (b) connect to the older bug - so that any logs 
are not misplaced.

There would probably need to be some sort of "This version is EOL, if 
you are still having this issue on a non-EOL version do X, Y, and Z"

Pat

-- 
Pat Riehecky
Scientific Linux developer

Fermi National Accelerator Laboratory
www.fnal.gov
www.scientificlinux.org