Hi Jason,
For core I agree with you, and we have had discussions about this in
the past and have come to the conclusion that we need to batch close
issues to be able to see what issues really needs to be worked on.
The work Michael has been doing however is not restricted to core
issues, it cover
+1 close em...
On Tue, Nov 25, 2014 at 4:22 PM, Jason van Zyl wrote:
> 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. B
+1 for Abandoned or Archived.
Won't Fix implies that some one has actually looked at it.
-Chris
Sent from my iPhone
On 26/11/2014, at 9:05 AM, Paul Benedict wrote:
> 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 w
Am 2014-11-25 um 23:05 schrieb Paul Benedict:
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
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
beca
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 y
Thanks for the praise Jason. Highly appreciated.
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 t
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 i
Am 2014-11-25 um 22:03 schrieb Dennis Lundberg:
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
Am 2014-11-24 um 23:05 schrieb 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.
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
Am 2014-11-24 um 23:05 schrieb 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.
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 sti
13 matches
Mail list logo
