On Mon, Oct 26, 2015 at 08:42:34AM -0400, Kaleb S. KEITHLEY wrote: > On 10/26/2015 05:14 AM, Niels de Vos wrote: > > On Wed, Oct 21, 2015 at 05:22:49AM -0400, Nagaprasad Sathyanarayana wrote: > >> I came across the following BZs which are still open in mainline. But > >> they are fixed and made available in a upstream release. Planning to > >> close them this week, unless there are any objections. > > > > We have a policy to close bugs when their patches land in a released > > version. The bugs against mainline will get closed when a release is > > made that contains those fixes. For many of the current mainline bugs, > > this would be the case when glusterfs-3.8 is released. > > Some of those bugs are pretty old. We haven't been good about closing > them when a 3.X.0 release has occurred. I sent email to the lists about > closing some of the older ones with a note to reopen them if they're > still valid. > > The bugs with RFE in the subject, or RFE or FutureFeature as a keyword > need to be left open after a 3.X.0 release if appropriate. > > I'm going to take a stab at guessing — based on the date the bug was > filed — at changing the version of the non-RFE bugs filed against mainline. In addition to this, I have a script that 1. checks bugzilla for a list of open bugs 2. queries Gerrit for each bug 3. checks the git repository for tags of merged changes A run earlier today, gave this as result: http://termbin.com/puiz We seem to have quite some bugs that have all their changes merged in a branch, before a tagged release was made. Those bugs should have been closed when the stable release was announced. You can identify them when you search for "Bug should be CLOSED". There are also quite some bugs that had patches posted, but may have been abandoned, or the patch does not have a "BUG: 0123456" tag or correct topic. Those bugs are marked with "No change posted, but " ... These all need some review, and either get closed as a duplicate, moved back to "NEW" or "ASSIGNED", or anything else that helps the reporter to understand the status. For example: https://bugzilla.redhat.com/show_bug.cgi?id=1213821#c4 I'll probably add my script to https://github.com/gluster/release-tools so that others can improve it where needed. But for the time being, would it be helpful to have the output emailed to gluster-devel once every week? Niels _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
