Kaleb S. KEITHLEY
2015-Sep-16 13:05 UTC
[Gluster-users] question about how to handle bugs filed against End-Of-Life versions of glusterfs
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
Atin Mukherjee
2015-Sep-16 15:31 UTC
[Gluster-users] question about how to handle bugs filed against End-Of-Life versions of glusterfs
-Atin Sent from one plus one On Sep 16, 2015 6:36 PM, "Kaleb S. KEITHLEY" <kkeithle at redhat.com> 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.I would go with option B as reassigning the bugs to n+ 1 release is a burden to release maintainer until a smart script does it for us. Otherwise its the reporter's responsibilities to open a new bug with the active version.> > 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 > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150916/036ee23e/attachment.html>
Pat Riehecky
2015-Sep-16 15:39 UTC
[Gluster-users] question about how to handle bugs filed against End-Of-Life versions of glusterfs
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
Sankarshan Mukhopadhyay
2015-Sep-16 15:49 UTC
[Gluster-users] [Gluster-devel] question about how to handle bugs filed against End-Of-Life versions of glusterfs
[for reference] On Wed, Sep 16, 2015 at 6:35 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote:> 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.<https://fedoraproject.org/wiki/BugZappers/HouseKeeping> - All bugs for EOL releases are automatically closed on the EOL date after providing a warning in the bug comments, 30 days prior to EOL. <https://fedoraproject.org/wiki/BugZappers/StockBugzillaResponses#End_of_Life_.28EOL.29_product> - The bug is reported against a version of Fedora that is no longer maintained.Thank you for your bug report.We are sorry, but the Fedora Project is no longer releasing bug fixes or any other updates for this version of Fedora. This bug will be set to CLOSED:WONTFIX to reflect this, but please reopen it if the problem persists after upgrading to the latest version of Fedora, which is available from:http://fedoraproject.org/get-fedora -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay>
Dave Warren
2015-Sep-22 05:58 UTC
[Gluster-users] question about how to handle bugs filed against End-Of-Life versions of glusterfs
On 2015-09-16 06:05, Kaleb S. KEITHLEY wrote:> The main difference is whether existing bugs are reassigned or simply > closed.Speaking as a user (and not a developer), little is more annoying than encountering a bug, spending time to research, reproduce and document a bug experienced in the current version, only to have it closed as DONTCARE and NOBODYLOOKED at a later date. I know that that isn't the intent here, and bugs against old versions often get fixed as code is updated and re-factored, and as such, bug reports often don't age well. Most open source projects aren't too bad, there are some that make it clear that only developer time is respected and no other contributions are valued, when the reality is that open source has the same need of QA, documentation and other time contributions that commercial software requires. At the same time, I understand what it can feel like to have a mountain of mostly-useless bugs that don't even apply to the current codebase, so there isn't any easy solution. So while I don't have a specific suggestion, I might encourage at least a cursory review of the bugs to determine which might still apply vs which are in code that was significantly refactored or otherwise likely resolved. (In all cases, bugs logged against versions which are out of support can definitely be closed immediately, if not blocked entirely) -- Dave Warren http://www.hireahit.com/ http://ca.linkedin.com/in/davejwarren
Kaleb S. KEITHLEY
2015-Sep-23 14:43 UTC
[Gluster-users] question about how to handle bugs filed against End-Of-Life versions of glusterfs
<top post> At today's Gluster Community meeting[3] it was decided ? taking into consideration the opinions expressed on the gluster-users and gluster-devel mailing lists ? that all bugs filed against end-of-life versions of glusterfs will be simply closed. I.e. CLOSED/WONTFIX. Bug submitters may reopen the bug if they believe the bug still exists in a newer version, updating the bug to indicate the newer version which the bug exists in. </top post> On 09/16/2015 09: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[3] http://meetbot.fedoraproject.org/gluster-meeting/2015-09-23/gluster-meeting.2015-09-23-12.01.log.html -- Kaleb