On Wed, Aug 17, 2016 at 09:41:22PM +0530, Atin Mukherjee wrote: > On Wednesday 17 August 2016, Kaleb S. KEITHLEY <kkeit...@redhat.com> wrote: > > > Hi, > > > > In today's Gluster Community Meeting it was tentatively agreed that we > > will change how we report the GlusterFS version for glusterfs bugs. > > > > Starting with the 3.9 release there will only be a "3.9" version in > > bugzilla; compared to the current scheme where there are, e.g., 3.8.0, > > 3.8.1, ..., 3.8.x versions in bugzilla. > > > May I ask what is the benefit we are going to get from this change? > Personally I am more inclined towards the existing option as users can > select the version and do not have to mention it in the comment. Sometimes > users may forget to report the version in the comment and we need to do > back and forth on this, instead having a specific release version on which > the bug can be filed looks a better option IMO.
On the other hand, reporters pick a random version, but have the exact package names+version in the #0 comment (which does not always match). The template also asks for the version and other required points, these should not be seen as optional. For bug triaging it makes query'ing sorting through bugs easier. Doing a regular expression search/match on versions is the only way we can currently construct complete lists of 3.7.x bugs. Being anle to query on version=3.7 should help all the maintainers in constructing their searches, rss-feeds and email filters. People should not report bugs against 3.7.13 and earlier 3.7.x versions anymore, those will not get updated in any case. The current notation suggests users that they can stay on a 3.7.x version, and get updates for them. I would like to encourage users to take 3.7 as a version, and they should not care (and update automatically) to the latest 3.7.x. Niels > > > > > When filing a new bug report, the exact version can — and should — be > > entered in the comments section of the report. > > > > For 3.8 and earlier we will retain the old scheme for the lifetime of > > that release. > > > > If you have any questions or comments about this change you can reply to > > this email or raise them in IRC #gluster-dev (on freenode) > > > > > > -- > > > > Kaleb > > > > > -- > --Atin > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-devel
signature.asc
Description: PGP signature
_______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
