Return-Path: X-Original-To: apmail-maven-dev-archive@www.apache.org Delivered-To: apmail-maven-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E556A10A8D for ; Tue, 25 Nov 2014 22:05:03 +0000 (UTC) Received: (qmail 88088 invoked by uid 500); 25 Nov 2014 22:05:03 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 87994 invoked by uid 500); 25 Nov 2014 22:05:03 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 87983 invoked by uid 99); 25 Nov 2014 22:05:03 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Nov 2014 22:05:03 +0000 Received: from mail-qc0-f169.google.com (mail-qc0-f169.google.com [209.85.216.169]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id D0BC31A048C for ; Tue, 25 Nov 2014 22:04:52 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id w7so1200051qcr.0 for ; Tue, 25 Nov 2014 14:05:02 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.88.100 with SMTP id s91mr39237761qgd.65.1416953102026; Tue, 25 Nov 2014 14:05:02 -0800 (PST) Received: by 10.96.209.13 with HTTP; Tue, 25 Nov 2014 14:05:01 -0800 (PST) In-Reply-To: <5474FBA2.4010202@apache.org> References: <5473AB9B.4090504@apache.org> <5474FBA2.4010202@apache.org> Date: Tue, 25 Nov 2014 16:05:01 -0600 Message-ID: Subject: Re: Abandoned bugs analysis From: Paul Benedict To: Maven Developers List Content-Type: multipart/alternative; boundary=001a11c119904f54cb0508b61ac7 --001a11c119904f54cb0508b61ac7 Content-Type: text/plain; charset=UTF-8 We did this bug clean up before so this isn't new to me. However, I do wonder if the resolution "Won't Fix" rubs people the wrong way? Maybe if we had an "Abandoned" resolution that would sit better. Aside from reading the comments in the ticket, it's not possible to know what was closed truly because something is intended never to be fixed and what was closed due to age. Cheers, Paul On Tue, Nov 25, 2014 at 3:58 PM, Michael Osipov wrote: > One postive response from MECLIPSE-196: Perfectly happy this was closed, > happy we're not using EARs any more. Can't wait to see new things coming > from takari. > > Am 2014-11-25 um 22:22 schrieb Jason van Zyl: > >> I don't agree. This is a project, not a product and if no one looks at >> something for 2 years then no one cares. We are not erasing the issues and >> if someone does care enough to ask to reopen an issue then that's great. >> But I've tried to purge down the list to something manageable twice now and >> it keeps growing so I highly appreciate what Michael is doing because it's >> unmanageable right now. And now that he's done that I have some motivation >> again to look through the issues so kudos to Michael. Nothing stops anyone >> from going through and reopening something, I don't think we need group >> scrubbing sessions. I think core committers need to go through and help >> curate the issues on a more regular basis. >> >> On Nov 25, 2014, at 4:03 PM, Dennis Lundberg wrote: >> >> Hi Michael >>> >>> Unfortunatelly, I think that 2 years of inactivity is way to short time. >>> I >>> wish it wasn't so, but the reality is that the age of an issue is not a >>> good indicator of whether the issue is valid or not. >>> >>> I think a better approach is to have joint bug scrub sessions, where we >>> join forces to manually check the validity of the issues. >>> >>> -- >>> Dennis Lundberg >>> Den 24 nov 2014 23:05 skrev "Michael Osipov" : >>> >>> Hi folks, >>>> >>>> I ran this query in JIRA: project in projectsWhereUserHasPermission >>>> ("Administer >>>> Projects") AND updated <= "2012-12-31" and resolution = Unresolved and >>>> type >>>> = Bug ORDER BY created desc >>>> >>>> Bugs which haven't been touched for almost two years. Total amount: >>>> *1139*. A lot of them are still Maven 1.x related 8-). >>>> >>>> Is there someone with bulk change abilities able to close those as >>>> "Won't >>>> Fix" with a note like: Big clean up end of 2014, you think that this >>>> issue >>>> still persists, reopen it? >>>> >>>> What do you think? >>>> >>>> Michael >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org >>>> For additional commands, e-mail: dev-help@maven.apache.org >>>> >>>> >>>> >> Thanks, >> >> Jason >> >> ---------------------------------------------------------- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> http://twitter.com/takari_io >> --------------------------------------------------------- >> >> the course of true love never did run smooth ... >> >> -- Shakespeare >> >> >> >> >> >> >> >> >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org > For additional commands, e-mail: dev-help@maven.apache.org > > --001a11c119904f54cb0508b61ac7--