The JIRA chocolate box

classic Classic list List threaded Threaded
30 messages Options
12
Reply | Threaded
Open this post in threaded view
|

The JIRA chocolate box

Benson Margulies
I just looked at the 'blocker' issues. We have a variety of very old
JIRAs here. None of the ones I looked at have a self-contained test
case that would can be downloaded, run, and converted to an
integration test, etc.

What's the policy? My temptation would be to comment on them asking if
the OP is still interested (in some cases, 5 years later), and, if so,
can they come up with a repeatable test case, and if not close as not
a real bug.

I don't mind in some cases doing work to build a test case, but to go
to all this trouble for a bug that was opened about maven 2.0.x, where
it may not be that easy to reconstruct the critical components of the
problem, seems a dubious use of time.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

stephenconnolly
+50

I say lets give each issue a ping, wait 2 weeks and close if no response

- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 18 Jun 2011 23:30, "Benson Margulies" <[hidden email]> wrote:

> I just looked at the 'blocker' issues. We have a variety of very old
> JIRAs here. None of the ones I looked at have a self-contained test
> case that would can be downloaded, run, and converted to an
> integration test, etc.
>
> What's the policy? My temptation would be to comment on them asking if
> the OP is still interested (in some cases, 5 years later), and, if so,
> can they come up with a repeatable test case, and if not close as not
> a real bug.
>
> I don't mind in some cases doing work to build a test case, but to go
> to all this trouble for a bug that was opened about maven 2.0.x, where
> it may not be that easy to reconstruct the critical components of the
> problem, seems a dubious use of time.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

stephenconnolly
they can always reopen if they want after the issue has been closed if the
2nd weeks was too short

- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 19 Jun 2011 00:20, "Stephen Connolly" <[hidden email]>
wrote:

> +50
>
> I say lets give each issue a ping, wait 2 weeks and close if no response
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mistakes, random nonsense
> words and other nonsense are a direct result of using swype to type on the
> screen
> On 18 Jun 2011 23:30, "Benson Margulies" <[hidden email]> wrote:
>> I just looked at the 'blocker' issues. We have a variety of very old
>> JIRAs here. None of the ones I looked at have a self-contained test
>> case that would can be downloaded, run, and converted to an
>> integration test, etc.
>>
>> What's the policy? My temptation would be to comment on them asking if
>> the OP is still interested (in some cases, 5 years later), and, if so,
>> can they come up with a repeatable test case, and if not close as not
>> a real bug.
>>
>> I don't mind in some cases doing work to build a test case, but to go
>> to all this trouble for a bug that was opened about maven 2.0.x, where
>> it may not be that easy to reconstruct the critical components of the
>> problem, seems a dubious use of time.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

Benson Margulies
If no one objects to this idea, I'd like to add a component, which is
an email like the following to the user list.

--snip--

Dear Maven Users,

Over the years, the JIRA for core Maven
(http://jira.codehaus.org/browse/MNG) has accumulated many unresolved
issues. All this clutter makes it difficult to tell where the real
problems are. Further, many of these issues do not contain
self-contained test cases. Practically speaking, it is very difficult
to diagnose and resolve a problem without a test case 'on the bench.'
We developers would like to turn over a bit of a new leaf. We're going
to ask you to supply a test case to go with your bug reports. In
return, we're going to try very hard to attend to them. You can tar it
up and attach it to the jira, or just push it to github and add a
link.

To clean up the current mess, we plan to start going through the
backlog. We'll add comments asking for test cases or other followup.
If we don't hear back in two weeks, we're going to close.

We're sorry for any frustration felt by the originators of
long-neglected reports, but we believe that this process will help us
be more responsive in the future.

--snip--


On Sat, Jun 18, 2011 at 7:22 PM, Stephen Connolly
<[hidden email]> wrote:

> they can always reopen if they want after the issue has been closed if the
> 2nd weeks was too short
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mistakes, random nonsense
> words and other nonsense are a direct result of using swype to type on the
> screen
> On 19 Jun 2011 00:20, "Stephen Connolly" <[hidden email]>
> wrote:
>> +50
>>
>> I say lets give each issue a ping, wait 2 weeks and close if no response
>>
>> - Stephen
>>
>> ---
>> Sent from my Android phone, so random spelling mistakes, random nonsense
>> words and other nonsense are a direct result of using swype to type on the
>> screen
>> On 18 Jun 2011 23:30, "Benson Margulies" <[hidden email]> wrote:
>>> I just looked at the 'blocker' issues. We have a variety of very old
>>> JIRAs here. None of the ones I looked at have a self-contained test
>>> case that would can be downloaded, run, and converted to an
>>> integration test, etc.
>>>
>>> What's the policy? My temptation would be to comment on them asking if
>>> the OP is still interested (in some cases, 5 years later), and, if so,
>>> can they come up with a repeatable test case, and if not close as not
>>> a real bug.
>>>
>>> I don't mind in some cases doing work to build a test case, but to go
>>> to all this trouble for a bug that was opened about maven 2.0.x, where
>>> it may not be that easy to reconstruct the critical components of the
>>> problem, seems a dubious use of time.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: The JIRA chocolate box

mgainty
In reply to this post by Benson Margulies

agreed
although scanning the Surefire JIRA i did notice some of jasons original jiras were'nt addressed for upwards of 3-4 years (by Brett Porter)

I havent heard of JIRA chocolate box..maybe an implementation of a Finite State Machine or perhaps this is a non sequitir?
Bedankt,
Martin
______________________________________________

> Date: Sat, 18 Jun 2011 18:30:04 -0400
> Subject: The JIRA chocolate box
> From: [hidden email]
> To: [hidden email]
>
> I just looked at the 'blocker' issues. We have a variety of very old
> JIRAs here. None of the ones I looked at have a self-contained test
> case that would can be downloaded, run, and converted to an
> integration test, etc.
>
> What's the policy? My temptation would be to comment on them asking if
> the OP is still interested (in some cases, 5 years later), and, if so,
> can they come up with a repeatable test case, and if not close as not
> a real bug.
>
> I don't mind in some cases doing work to build a test case, but to go
> to all this trouble for a bug that was opened about maven 2.0.x, where
> it may not be that easy to reconstruct the critical components of the
> problem, seems a dubious use of time.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
     
Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

Ralph Goers
My guess is a reference to Forrest Gump - you never know what you are going to get.

Ralph

On Jun 18, 2011, at 7:51 PM, Martin Gainty wrote:

>
> agreed
> although scanning the Surefire JIRA i did notice some of jasons original jiras were'nt addressed for upwards of 3-4 years (by Brett Porter)
>
> I havent heard of JIRA chocolate box..maybe an implementation of a Finite State Machine or perhaps this is a non sequitir?
> Bedankt,
> Martin
> ______________________________________________
>
>> Date: Sat, 18 Jun 2011 18:30:04 -0400
>> Subject: The JIRA chocolate box
>> From: [hidden email]
>> To: [hidden email]
>>
>> I just looked at the 'blocker' issues. We have a variety of very old
>> JIRAs here. None of the ones I looked at have a self-contained test
>> case that would can be downloaded, run, and converted to an
>> integration test, etc.
>>
>> What's the policy? My temptation would be to comment on them asking if
>> the OP is still interested (in some cases, 5 years later), and, if so,
>> can they come up with a repeatable test case, and if not close as not
>> a real bug.
>>
>> I don't mind in some cases doing work to build a test case, but to go
>> to all this trouble for a bug that was opened about maven 2.0.x, where
>> it may not be that easy to reconstruct the critical components of the
>> problem, seems a dubious use of time.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>    


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

Benson Margulies
I am only proposing this for MNG at this point.

On Jun 18, 2011, at 10:55 PM, Ralph Goers <[hidden email]> wrote:

> My guess is a reference to Forrest Gump - you never know what you are going to get.
>
> Ralph
>
> On Jun 18, 2011, at 7:51 PM, Martin Gainty wrote:
>
>>
>> agreed
>> although scanning the Surefire JIRA i did notice some of jasons original jiras were'nt addressed for upwards of 3-4 years (by Brett Porter)
>>
>> I havent heard of JIRA chocolate box..maybe an implementation of a Finite State Machine or perhaps this is a non sequitir?
>> Bedankt,
>> Martin
>> ______________________________________________
>>
>>> Date: Sat, 18 Jun 2011 18:30:04 -0400
>>> Subject: The JIRA chocolate box
>>> From: [hidden email]
>>> To: [hidden email]
>>>
>>> I just looked at the 'blocker' issues. We have a variety of very old
>>> JIRAs here. None of the ones I looked at have a self-contained test
>>> case that would can be downloaded, run, and converted to an
>>> integration test, etc.
>>>
>>> What's the policy? My temptation would be to comment on them asking if
>>> the OP is still interested (in some cases, 5 years later), and, if so,
>>> can they come up with a repeatable test case, and if not close as not
>>> a real bug.
>>>
>>> I don't mind in some cases doing work to build a test case, but to go
>>> to all this trouble for a bug that was opened about maven 2.0.x, where
>>> it may not be that easy to reconstruct the critical components of the
>>> problem, seems a dubious use of time.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: The JIRA chocolate box

mgainty
In reply to this post by Ralph Goers

> Subject: Re: The JIRA chocolate box
> From: [hidden email]
> Date: Sat, 18 Jun 2011 19:54:30 -0700
> To: [hidden email]
>
> My guess is a reference to Forrest Gump - you never know what you are going to get.
>
> Ralph
MG>and thats all i have to say about that!...MG
MG>Thanks Ralph

>
> On Jun 18, 2011, at 7:51 PM, Martin Gainty wrote:
>
> >
> > agreed
> > although scanning the Surefire JIRA i did notice some of jasons original jiras were'nt addressed for upwards of 3-4 years (by Brett Porter)
> >
> > I havent heard of JIRA chocolate box..maybe an implementation of a Finite State Machine or perhaps this is a non sequitir?
> > Bedankt,
> > Martin
> > ______________________________________________
> >
> >> Date: Sat, 18 Jun 2011 18:30:04 -0400
> >> Subject: The JIRA chocolate box
> >> From: [hidden email]
> >> To: [hidden email]
> >>
> >> I just looked at the 'blocker' issues. We have a variety of very old
> >> JIRAs here. None of the ones I looked at have a self-contained test
> >> case that would can be downloaded, run, and converted to an
> >> integration test, etc.
> >>
> >> What's the policy? My temptation would be to comment on them asking if
> >> the OP is still interested (in some cases, 5 years later), and, if so,
> >> can they come up with a repeatable test case, and if not close as not
> >> a real bug.
> >>
> >> I don't mind in some cases doing work to build a test case, but to go
> >> to all this trouble for a bug that was opened about maven 2.0.x, where
> >> it may not be that easy to reconstruct the critical components of the
> >> problem, seems a dubious use of time.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >    
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
     
Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

Mark Struberg
In reply to this post by Benson Margulies
a very good idea

+1

LieGrue,
strub

--- On Sun, 6/19/11, Benson Margulies <[hidden email]> wrote:

> From: Benson Margulies <[hidden email]>
> Subject: Re: The JIRA chocolate box
> To: "Maven Developers List" <[hidden email]>
> Date: Sunday, June 19, 2011, 3:05 AM
> I am only proposing this for MNG at
> this point.
>
> On Jun 18, 2011, at 10:55 PM, Ralph Goers <[hidden email]>
> wrote:
>
> > My guess is a reference to Forrest Gump - you never
> know what you are going to get.
> >
> > Ralph
> >
> > On Jun 18, 2011, at 7:51 PM, Martin Gainty wrote:
> >
> >>
> >> agreed
> >> although scanning the Surefire JIRA i did notice
> some of jasons original jiras were'nt addressed for upwards
> of 3-4 years (by Brett Porter)
> >>
> >> I havent heard of JIRA chocolate box..maybe an
> implementation of a Finite State Machine or perhaps this is
> a non sequitir?
> >> Bedankt,
> >> Martin
> >> ______________________________________________
> >>
> >>> Date: Sat, 18 Jun 2011 18:30:04 -0400
> >>> Subject: The JIRA chocolate box
> >>> From: [hidden email]
> >>> To: [hidden email]
> >>>
> >>> I just looked at the 'blocker' issues. We have
> a variety of very old
> >>> JIRAs here. None of the ones I looked at have
> a self-contained test
> >>> case that would can be downloaded, run, and
> converted to an
> >>> integration test, etc.
> >>>
> >>> What's the policy? My temptation would be to
> comment on them asking if
> >>> the OP is still interested (in some cases, 5
> years later), and, if so,
> >>> can they come up with a repeatable test case,
> and if not close as not
> >>> a real bug.
> >>>
> >>> I don't mind in some cases doing work to build
> a test case, but to go
> >>> to all this trouble for a bug that was opened
> about maven 2.0.x, where
> >>> it may not be that easy to reconstruct the
> critical components of the
> >>> problem, seems a dubious use of time.
> >>>
> >>>
> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [hidden email]
> >>> For additional commands, e-mail: [hidden email]
> >>>
> >>
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

Olivier Lamy
In reply to this post by Benson Margulies
Nice idea +1.

BTW asking a test case is not very easy.
As most of the time issues happen on corpo/private *complex* project.
So extracting a test case can be hard.

2011/6/19 Benson Margulies <[hidden email]>:

> If no one objects to this idea, I'd like to add a component, which is
> an email like the following to the user list.
>
> --snip--
>
> Dear Maven Users,
>
> Over the years, the JIRA for core Maven
> (http://jira.codehaus.org/browse/MNG) has accumulated many unresolved
> issues. All this clutter makes it difficult to tell where the real
> problems are. Further, many of these issues do not contain
> self-contained test cases. Practically speaking, it is very difficult
> to diagnose and resolve a problem without a test case 'on the bench.'
> We developers would like to turn over a bit of a new leaf. We're going
> to ask you to supply a test case to go with your bug reports. In
> return, we're going to try very hard to attend to them. You can tar it
> up and attach it to the jira, or just push it to github and add a
> link.
>
> To clean up the current mess, we plan to start going through the
> backlog. We'll add comments asking for test cases or other followup.
> If we don't hear back in two weeks, we're going to close.
>
> We're sorry for any frustration felt by the originators of
> long-neglected reports, but we believe that this process will help us
> be more responsive in the future.
>
> --snip--
>
>
> On Sat, Jun 18, 2011 at 7:22 PM, Stephen Connolly
> <[hidden email]> wrote:
>> they can always reopen if they want after the issue has been closed if the
>> 2nd weeks was too short
>>
>> - Stephen
>>
>> ---
>> Sent from my Android phone, so random spelling mistakes, random nonsense
>> words and other nonsense are a direct result of using swype to type on the
>> screen
>> On 19 Jun 2011 00:20, "Stephen Connolly" <[hidden email]>
>> wrote:
>>> +50
>>>
>>> I say lets give each issue a ping, wait 2 weeks and close if no response
>>>
>>> - Stephen
>>>
>>> ---
>>> Sent from my Android phone, so random spelling mistakes, random nonsense
>>> words and other nonsense are a direct result of using swype to type on the
>>> screen
>>> On 18 Jun 2011 23:30, "Benson Margulies" <[hidden email]> wrote:
>>>> I just looked at the 'blocker' issues. We have a variety of very old
>>>> JIRAs here. None of the ones I looked at have a self-contained test
>>>> case that would can be downloaded, run, and converted to an
>>>> integration test, etc.
>>>>
>>>> What's the policy? My temptation would be to comment on them asking if
>>>> the OP is still interested (in some cases, 5 years later), and, if so,
>>>> can they come up with a repeatable test case, and if not close as not
>>>> a real bug.
>>>>
>>>> I don't mind in some cases doing work to build a test case, but to go
>>>> to all this trouble for a bug that was opened about maven 2.0.x, where
>>>> it may not be that easy to reconstruct the critical components of the
>>>> problem, seems a dubious use of time.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>



--
Olivier Lamy
http://twitter.com/olamy | http://www.linkedin.com/in/olamy

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

Dennis Lundberg-2
In reply to this post by Benson Margulies
On 2011-06-19 00:30, Benson Margulies wrote:
> I just looked at the 'blocker' issues. We have a variety of very old
> JIRAs here. None of the ones I looked at have a self-contained test
> case that would can be downloaded, run, and converted to an
> integration test, etc.

This is one of the major obstacles we have at the Maven project. The
sheer amount of old and sometimes really old issues in JIRA. For the
last couple of years I've pinged reporters of new issues straight away
for test cases, if none was attached to a new issue. But as you say
there are lots of old ones that are practically impossible to resolve
without some kind of test case.

Maybe we should plan a JIRA cleanup day? Let's find a date where some of
us on the dev team can work together to clean up old issues. We announce
that together with your proposed letter to the users list as well.

> What's the policy? My temptation would be to comment on them asking if
> the OP is still interested (in some cases, 5 years later), and, if so,
> can they come up with a repeatable test case, and if not close as not
> a real bug.

I've done this kind of thing for plugins in the past. For those I have
opted to close the issue as "Incomplete", because it lacks a
reproducible test case.

> I don't mind in some cases doing work to build a test case, but to go
> to all this trouble for a bug that was opened about maven 2.0.x, where
> it may not be that easy to reconstruct the critical components of the
> problem, seems a dubious use of time.

Agreed.

>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

Dennis Lundberg-2
In reply to this post by Benson Margulies
This is a great idea.
Some minor comments inline.


On 2011-06-19 04:22, Benson Margulies wrote:

> If no one objects to this idea, I'd like to add a component, which is
> an email like the following to the user list.
>
> --snip--
>
> Dear Maven Users,
>
> Over the years, the JIRA for core Maven
> (http://jira.codehaus.org/browse/MNG) has accumulated many unresolved
> issues. All this clutter makes it difficult to tell where the real
> problems are. Further, many of these issues do not contain
> self-contained test cases. Practically speaking, it is very difficult
> to diagnose and resolve a problem without a test case 'on the bench.'
> We developers would like to turn over a bit of a new leaf. We're going
> to ask you to supply a test case to go with your bug reports. In
> return, we're going to try very hard to attend to them. You can tar it
> up and attach it to the jira, or just push it to github and add a
> link.

Over the years I've sometimes had problems reading tar files attached to
JIRA from users on my Windows machine, even though I have the proper
tools for it. I think ZIP of JAR files are generally more portable than
TAR files.

To be able to keep our stuff in one place, I prefer attached compressed
archives in JIRA over something pushed to GitHub. What happens if
someone, after a couple of years, wants to download the test case and
github no longer exists.

> To clean up the current mess, we plan to start going through the
> backlog. We'll add comments asking for test cases or other followup.
> If we don't hear back in two weeks, we're going to close.
>
> We're sorry for any frustration felt by the originators of
> long-neglected reports, but we believe that this process will help us
> be more responsive in the future.

Excellent stuff!

> --snip--
>
>
> On Sat, Jun 18, 2011 at 7:22 PM, Stephen Connolly
> <[hidden email]> wrote:
>> they can always reopen if they want after the issue has been closed if the
>> 2nd weeks was too short
>>
>> - Stephen
>>
>> ---
>> Sent from my Android phone, so random spelling mistakes, random nonsense
>> words and other nonsense are a direct result of using swype to type on the
>> screen
>> On 19 Jun 2011 00:20, "Stephen Connolly" <[hidden email]>
>> wrote:
>>> +50
>>>
>>> I say lets give each issue a ping, wait 2 weeks and close if no response
>>>
>>> - Stephen
>>>
>>> ---
>>> Sent from my Android phone, so random spelling mistakes, random nonsense
>>> words and other nonsense are a direct result of using swype to type on the
>>> screen
>>> On 18 Jun 2011 23:30, "Benson Margulies" <[hidden email]> wrote:
>>>> I just looked at the 'blocker' issues. We have a variety of very old
>>>> JIRAs here. None of the ones I looked at have a self-contained test
>>>> case that would can be downloaded, run, and converted to an
>>>> integration test, etc.
>>>>
>>>> What's the policy? My temptation would be to comment on them asking if
>>>> the OP is still interested (in some cases, 5 years later), and, if so,
>>>> can they come up with a repeatable test case, and if not close as not
>>>> a real bug.
>>>>
>>>> I don't mind in some cases doing work to build a test case, but to go
>>>> to all this trouble for a bug that was opened about maven 2.0.x, where
>>>> it may not be that easy to reconstruct the critical components of the
>>>> problem, seems a dubious use of time.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

sebb-2-2
In reply to this post by Dennis Lundberg-2
On 19 June 2011 11:52, Dennis Lundberg <[hidden email]> wrote:

> On 2011-06-19 00:30, Benson Margulies wrote:
>> I just looked at the 'blocker' issues. We have a variety of very old
>> JIRAs here. None of the ones I looked at have a self-contained test
>> case that would can be downloaded, run, and converted to an
>> integration test, etc.
>
> This is one of the major obstacles we have at the Maven project. The
> sheer amount of old and sometimes really old issues in JIRA. For the
> last couple of years I've pinged reporters of new issues straight away
> for test cases, if none was attached to a new issue. But as you say
> there are lots of old ones that are practically impossible to resolve
> without some kind of test case.
>
> Maybe we should plan a JIRA cleanup day? Let's find a date where some of
> us on the dev team can work together to clean up old issues. We announce
> that together with your proposed letter to the users list as well.
>
>> What's the policy? My temptation would be to comment on them asking if
>> the OP is still interested (in some cases, 5 years later), and, if so,
>> can they come up with a repeatable test case, and if not close as not
>> a real bug.
>
> I've done this kind of thing for plugins in the past. For those I have
> opted to close the issue as "Incomplete", because it lacks a
> reproducible test case.

+1

This will make it easier to find later if necessary.

I think it's vital that the resolution distinguish such cases from
fixed bugs and non-bugs.

>> I don't mind in some cases doing work to build a test case, but to go
>> to all this trouble for a bug that was opened about maven 2.0.x, where
>> it may not be that easy to reconstruct the critical components of the
>> problem, seems a dubious use of time.
>
> Agreed.
>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

Benson Margulies
FWIW, I've spent plenty of time on the 'trying to make a test case'
side of the fence and I appreciate how hard it can be.

If someone makes a cogent case that they can't come with a testcase,
then there are possible outcomes:

1: A dev finds the story sufficiently compelling to try to build a
test case or otherwise analyze the problem, soon enough that the
caravan does not move on.
1a: they come up with something and the OP can confirm that it fixes things.
1b: they are stumped or whatever they come with doesn't work.
2: no one in the dev community is willing to tackle.

In short, stating this policy doesn't stop us from trying to be
helpful in the impossible case, I just think that we should be
realistic in declaring failure to avoid recreating the compost heap.

As for github, I don't mind having the email stick to 'attach a zip'.
There are cases where github, or even, 'this svn URL of another Apache
project' allows collaboration with the OP in refining a test case, but
OPs will think of this for themselves.

I don't know that we need a JIRA day; we need everyone willing on dev@
to start digging down the JIRAs pinging.

On Sun, Jun 19, 2011 at 7:02 AM, sebb <[hidden email]> wrote:

> On 19 June 2011 11:52, Dennis Lundberg <[hidden email]> wrote:
>> On 2011-06-19 00:30, Benson Margulies wrote:
>>> I just looked at the 'blocker' issues. We have a variety of very old
>>> JIRAs here. None of the ones I looked at have a self-contained test
>>> case that would can be downloaded, run, and converted to an
>>> integration test, etc.
>>
>> This is one of the major obstacles we have at the Maven project. The
>> sheer amount of old and sometimes really old issues in JIRA. For the
>> last couple of years I've pinged reporters of new issues straight away
>> for test cases, if none was attached to a new issue. But as you say
>> there are lots of old ones that are practically impossible to resolve
>> without some kind of test case.
>>
>> Maybe we should plan a JIRA cleanup day? Let's find a date where some of
>> us on the dev team can work together to clean up old issues. We announce
>> that together with your proposed letter to the users list as well.
>>
>>> What's the policy? My temptation would be to comment on them asking if
>>> the OP is still interested (in some cases, 5 years later), and, if so,
>>> can they come up with a repeatable test case, and if not close as not
>>> a real bug.
>>
>> I've done this kind of thing for plugins in the past. For those I have
>> opted to close the issue as "Incomplete", because it lacks a
>> reproducible test case.
>
> +1
>
> This will make it easier to find later if necessary.
>
> I think it's vital that the resolution distinguish such cases from
> fixed bugs and non-bugs.
>
>>> I don't mind in some cases doing work to build a test case, but to go
>>> to all this trouble for a bug that was opened about maven 2.0.x, where
>>> it may not be that easy to reconstruct the critical components of the
>>> problem, seems a dubious use of time.
>>
>> Agreed.
>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>>
>> --
>> Dennis Lundberg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

jdcasey
In reply to this post by Benson Margulies
+1

Great idea!

On 6/18/11 10:22 PM, Benson Margulies wrote:

> If no one objects to this idea, I'd like to add a component, which is
> an email like the following to the user list.
>
> --snip--
>
> Dear Maven Users,
>
> Over the years, the JIRA for core Maven
> (http://jira.codehaus.org/browse/MNG) has accumulated many unresolved
> issues. All this clutter makes it difficult to tell where the real
> problems are. Further, many of these issues do not contain
> self-contained test cases. Practically speaking, it is very difficult
> to diagnose and resolve a problem without a test case 'on the bench.'
> We developers would like to turn over a bit of a new leaf. We're going
> to ask you to supply a test case to go with your bug reports. In
> return, we're going to try very hard to attend to them. You can tar it
> up and attach it to the jira, or just push it to github and add a
> link.
>
> To clean up the current mess, we plan to start going through the
> backlog. We'll add comments asking for test cases or other followup.
> If we don't hear back in two weeks, we're going to close.
>
> We're sorry for any frustration felt by the originators of
> long-neglected reports, but we believe that this process will help us
> be more responsive in the future.
>
> --snip--
>
>
> On Sat, Jun 18, 2011 at 7:22 PM, Stephen Connolly
> <[hidden email]>  wrote:
>> they can always reopen if they want after the issue has been closed if the
>> 2nd weeks was too short
>>
>> - Stephen
>>
>> ---
>> Sent from my Android phone, so random spelling mistakes, random nonsense
>> words and other nonsense are a direct result of using swype to type on the
>> screen
>> On 19 Jun 2011 00:20, "Stephen Connolly"<[hidden email]>
>> wrote:
>>> +50
>>>
>>> I say lets give each issue a ping, wait 2 weeks and close if no response
>>>
>>> - Stephen
>>>
>>> ---
>>> Sent from my Android phone, so random spelling mistakes, random nonsense
>>> words and other nonsense are a direct result of using swype to type on the
>>> screen
>>> On 18 Jun 2011 23:30, "Benson Margulies"<[hidden email]>  wrote:
>>>> I just looked at the 'blocker' issues. We have a variety of very old
>>>> JIRAs here. None of the ones I looked at have a self-contained test
>>>> case that would can be downloaded, run, and converted to an
>>>> integration test, etc.
>>>>
>>>> What's the policy? My temptation would be to comment on them asking if
>>>> the OP is still interested (in some cases, 5 years later), and, if so,
>>>> can they come up with a repeatable test case, and if not close as not
>>>> a real bug.
>>>>
>>>> I don't mind in some cases doing work to build a test case, but to go
>>>> to all this trouble for a bug that was opened about maven 2.0.x, where
>>>> it may not be that easy to reconstruct the critical components of the
>>>> problem, seems a dubious use of time.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

Kristian Rosenvold-4
Is there any smart way to tag a bug as processed in a triaging process
so we can focus on the remaining bugs?

I've always wondered if there's any option to tag an issue or create
shared custom lists...?

K

Den 19. juni 2011 kl. 18:42 skrev John Casey <[hidden email]>:

> +1
>
> Great idea!
>
> On 6/18/11 10:22 PM, Benson Margulies wrote:
>> If no one objects to this idea, I'd like to add a component, which is
>> an email like the following to the user list.
>>
>> --snip--
>>
>> Dear Maven Users,
>>
>> Over the years, the JIRA for core Maven
>> (http://jira.codehaus.org/browse/MNG) has accumulated many unresolved
>> issues. All this clutter makes it difficult to tell where the real
>> problems are. Further, many of these issues do not contain
>> self-contained test cases. Practically speaking, it is very difficult
>> to diagnose and resolve a problem without a test case 'on the bench.'
>> We developers would like to turn over a bit of a new leaf. We're going
>> to ask you to supply a test case to go with your bug reports. In
>> return, we're going to try very hard to attend to them. You can tar it
>> up and attach it to the jira, or just push it to github and add a
>> link.
>>
>> To clean up the current mess, we plan to start going through the
>> backlog. We'll add comments asking for test cases or other followup.
>> If we don't hear back in two weeks, we're going to close.
>>
>> We're sorry for any frustration felt by the originators of
>> long-neglected reports, but we believe that this process will help us
>> be more responsive in the future.
>>
>> --snip--
>>
>>
>> On Sat, Jun 18, 2011 at 7:22 PM, Stephen Connolly
>> <[hidden email]> wrote:
>>> they can always reopen if they want after the issue has been closed if the
>>> 2nd weeks was too short
>>>
>>> - Stephen
>>>
>>> ---
>>> Sent from my Android phone, so random spelling mistakes, random nonsense
>>> words and other nonsense are a direct result of using swype to type on the
>>> screen
>>> On 19 Jun 2011 00:20, "Stephen Connolly"<[hidden email]>
>>> wrote:
>>>> +50
>>>>
>>>> I say lets give each issue a ping, wait 2 weeks and close if no response
>>>>
>>>> - Stephen
>>>>
>>>> ---
>>>> Sent from my Android phone, so random spelling mistakes, random nonsense
>>>> words and other nonsense are a direct result of using swype to type on the
>>>> screen
>>>> On 18 Jun 2011 23:30, "Benson Margulies"<[hidden email]>  wrote:
>>>>> I just looked at the 'blocker' issues. We have a variety of very old
>>>>> JIRAs here. None of the ones I looked at have a self-contained test
>>>>> case that would can be downloaded, run, and converted to an
>>>>> integration test, etc.
>>>>>
>>>>> What's the policy? My temptation would be to comment on them asking if
>>>>> the OP is still interested (in some cases, 5 years later), and, if so,
>>>>> can they come up with a repeatable test case, and if not close as not
>>>>> a real bug.
>>>>>
>>>>> I don't mind in some cases doing work to build a test case, but to go
>>>>> to all this trouble for a bug that was opened about maven 2.0.x, where
>>>>> it may not be that easy to reconstruct the critical components of the
>>>>> problem, seems a dubious use of time.
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [hidden email]
>>>>> For additional commands, e-mail: [hidden email]
>>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.johnofalltrades.name/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

Dennis Lundberg-2
On 2011-06-19 18:46, Kristian Rosenvold wrote:
> Is there any smart way to tag a bug as processed in a triaging process
> so we can focus on the remaining bugs?
>
> I've always wondered if there's any option to tag an issue or create
> shared custom lists...?

We should be able to use "Labels" for this:
http://confluence.atlassian.com/display/JIRA043/Labelling+an+Issue

I haven't used them myself yet, but they seem to fit the bill.


>
> K
>
> Den 19. juni 2011 kl. 18:42 skrev John Casey <[hidden email]>:
>
>> +1
>>
>> Great idea!
>>
>> On 6/18/11 10:22 PM, Benson Margulies wrote:
>>> If no one objects to this idea, I'd like to add a component, which is
>>> an email like the following to the user list.
>>>
>>> --snip--
>>>
>>> Dear Maven Users,
>>>
>>> Over the years, the JIRA for core Maven
>>> (http://jira.codehaus.org/browse/MNG) has accumulated many unresolved
>>> issues. All this clutter makes it difficult to tell where the real
>>> problems are. Further, many of these issues do not contain
>>> self-contained test cases. Practically speaking, it is very difficult
>>> to diagnose and resolve a problem without a test case 'on the bench.'
>>> We developers would like to turn over a bit of a new leaf. We're going
>>> to ask you to supply a test case to go with your bug reports. In
>>> return, we're going to try very hard to attend to them. You can tar it
>>> up and attach it to the jira, or just push it to github and add a
>>> link.
>>>
>>> To clean up the current mess, we plan to start going through the
>>> backlog. We'll add comments asking for test cases or other followup.
>>> If we don't hear back in two weeks, we're going to close.
>>>
>>> We're sorry for any frustration felt by the originators of
>>> long-neglected reports, but we believe that this process will help us
>>> be more responsive in the future.
>>>
>>> --snip--
>>>
>>>
>>> On Sat, Jun 18, 2011 at 7:22 PM, Stephen Connolly
>>> <[hidden email]> wrote:
>>>> they can always reopen if they want after the issue has been closed if the
>>>> 2nd weeks was too short
>>>>
>>>> - Stephen
>>>>
>>>> ---
>>>> Sent from my Android phone, so random spelling mistakes, random nonsense
>>>> words and other nonsense are a direct result of using swype to type on the
>>>> screen
>>>> On 19 Jun 2011 00:20, "Stephen Connolly"<[hidden email]>
>>>> wrote:
>>>>> +50
>>>>>
>>>>> I say lets give each issue a ping, wait 2 weeks and close if no response
>>>>>
>>>>> - Stephen
>>>>>
>>>>> ---
>>>>> Sent from my Android phone, so random spelling mistakes, random nonsense
>>>>> words and other nonsense are a direct result of using swype to type on the
>>>>> screen
>>>>> On 18 Jun 2011 23:30, "Benson Margulies"<[hidden email]>  wrote:
>>>>>> I just looked at the 'blocker' issues. We have a variety of very old
>>>>>> JIRAs here. None of the ones I looked at have a self-contained test
>>>>>> case that would can be downloaded, run, and converted to an
>>>>>> integration test, etc.
>>>>>>
>>>>>> What's the policy? My temptation would be to comment on them asking if
>>>>>> the OP is still interested (in some cases, 5 years later), and, if so,
>>>>>> can they come up with a repeatable test case, and if not close as not
>>>>>> a real bug.
>>>>>>
>>>>>> I don't mind in some cases doing work to build a test case, but to go
>>>>>> to all this trouble for a bug that was opened about maven 2.0.x, where
>>>>>> it may not be that easy to reconstruct the critical components of the
>>>>>> problem, seems a dubious use of time.
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: [hidden email]
>>>>>> For additional commands, e-mail: [hidden email]
>>>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> Blog: http://www.johnofalltrades.name/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

Arnaud Héritier
Labels are now a native feature in recent releases of Jira and they are
really useful to tag issues for a need like this one.
We could use them also to give a complexity level of the issue, ...
The need is to define them and follow a common convention

Another solution is to have a custom workflow with a default state "Need
Triage" and additional status like "Verified" ...
This is what they have @ Atlassian if i remember well.
It's not really difficult to create if we want.
The only limitation is that we need to be admin of the jira instance to
create our own workflow.

Arnaud, who is fighting in // to upgrade a Jira 4.2 instance to 4.3 ....

On Sun, Jun 19, 2011 at 7:13 PM, Dennis Lundberg <[hidden email]> wrote:

> On 2011-06-19 18:46, Kristian Rosenvold wrote:
> > Is there any smart way to tag a bug as processed in a triaging process
> > so we can focus on the remaining bugs?
> >
> > I've always wondered if there's any option to tag an issue or create
> > shared custom lists...?
>
> We should be able to use "Labels" for this:
> http://confluence.atlassian.com/display/JIRA043/Labelling+an+Issue
>
> I haven't used them myself yet, but they seem to fit the bill.
>
>
> >
> > K
> >
> > Den 19. juni 2011 kl. 18:42 skrev John Casey <[hidden email]>:
> >
> >> +1
> >>
> >> Great idea!
> >>
> >> On 6/18/11 10:22 PM, Benson Margulies wrote:
> >>> If no one objects to this idea, I'd like to add a component, which is
> >>> an email like the following to the user list.
> >>>
> >>> --snip--
> >>>
> >>> Dear Maven Users,
> >>>
> >>> Over the years, the JIRA for core Maven
> >>> (http://jira.codehaus.org/browse/MNG) has accumulated many unresolved
> >>> issues. All this clutter makes it difficult to tell where the real
> >>> problems are. Further, many of these issues do not contain
> >>> self-contained test cases. Practically speaking, it is very difficult
> >>> to diagnose and resolve a problem without a test case 'on the bench.'
> >>> We developers would like to turn over a bit of a new leaf. We're going
> >>> to ask you to supply a test case to go with your bug reports. In
> >>> return, we're going to try very hard to attend to them. You can tar it
> >>> up and attach it to the jira, or just push it to github and add a
> >>> link.
> >>>
> >>> To clean up the current mess, we plan to start going through the
> >>> backlog. We'll add comments asking for test cases or other followup.
> >>> If we don't hear back in two weeks, we're going to close.
> >>>
> >>> We're sorry for any frustration felt by the originators of
> >>> long-neglected reports, but we believe that this process will help us
> >>> be more responsive in the future.
> >>>
> >>> --snip--
> >>>
> >>>
> >>> On Sat, Jun 18, 2011 at 7:22 PM, Stephen Connolly
> >>> <[hidden email]> wrote:
> >>>> they can always reopen if they want after the issue has been closed if
> the
> >>>> 2nd weeks was too short
> >>>>
> >>>> - Stephen
> >>>>
> >>>> ---
> >>>> Sent from my Android phone, so random spelling mistakes, random
> nonsense
> >>>> words and other nonsense are a direct result of using swype to type on
> the
> >>>> screen
> >>>> On 19 Jun 2011 00:20, "Stephen Connolly"<
> [hidden email]>
> >>>> wrote:
> >>>>> +50
> >>>>>
> >>>>> I say lets give each issue a ping, wait 2 weeks and close if no
> response
> >>>>>
> >>>>> - Stephen
> >>>>>
> >>>>> ---
> >>>>> Sent from my Android phone, so random spelling mistakes, random
> nonsense
> >>>>> words and other nonsense are a direct result of using swype to type
> on the
> >>>>> screen
> >>>>> On 18 Jun 2011 23:30, "Benson Margulies"<[hidden email]>
>  wrote:
> >>>>>> I just looked at the 'blocker' issues. We have a variety of very old
> >>>>>> JIRAs here. None of the ones I looked at have a self-contained test
> >>>>>> case that would can be downloaded, run, and converted to an
> >>>>>> integration test, etc.
> >>>>>>
> >>>>>> What's the policy? My temptation would be to comment on them asking
> if
> >>>>>> the OP is still interested (in some cases, 5 years later), and, if
> so,
> >>>>>> can they come up with a repeatable test case, and if not close as
> not
> >>>>>> a real bug.
> >>>>>>
> >>>>>> I don't mind in some cases doing work to build a test case, but to
> go
> >>>>>> to all this trouble for a bug that was opened about maven 2.0.x,
> where
> >>>>>> it may not be that easy to reconstruct the critical components of
> the
> >>>>>> problem, seems a dubious use of time.
> >>>>>>
> >>>>>>
> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: [hidden email]
> >>>>>> For additional commands, e-mail: [hidden email]
> >>>>>>
> >>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [hidden email]
> >>> For additional commands, e-mail: [hidden email]
> >>>
> >>
> >> --
> >> John Casey
> >> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> >> Blog: http://www.johnofalltrades.name/
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

Daniel  Kulp
In reply to this post by Dennis Lundberg-2
On Sunday, June 19, 2011 7:13:11 PM Dennis Lundberg wrote:

> On 2011-06-19 18:46, Kristian Rosenvold wrote:
> > Is there any smart way to tag a bug as processed in a triaging process
> > so we can focus on the remaining bugs?
> >
> > I've always wondered if there's any option to tag an issue or create
> > shared custom lists...?
>
> We should be able to use "Labels" for this:
> http://confluence.atlassian.com/display/JIRA043/Labelling+an+Issue
>
> I haven't used them myself yet, but they seem to fit the bill.

For CXF, we have a special "NeedMoreInfo" version that we use for this.   We
set the "FixFor" version to that when we've added a comment that requires more
information from the user.   We can easily get a list of all the issues that
require more information, when we asked for it, etc.....  

Probably an abuse of the version field though.   :-)

Dan


>
> > K
> >
> > Den 19. juni 2011 kl. 18:42 skrev John Casey <[hidden email]>:
> >> +1
> >>
> >> Great idea!
> >>
> >> On 6/18/11 10:22 PM, Benson Margulies wrote:
> >>> If no one objects to this idea, I'd like to add a component, which
> >>> is
> >>> an email like the following to the user list.
> >>>
> >>> --snip--
> >>>
> >>> Dear Maven Users,
> >>>
> >>> Over the years, the JIRA for core Maven
> >>> (http://jira.codehaus.org/browse/MNG) has accumulated many
> >>> unresolved
> >>> issues. All this clutter makes it difficult to tell where the real
> >>> problems are. Further, many of these issues do not contain
> >>> self-contained test cases. Practically speaking, it is very
> >>> difficult
> >>> to diagnose and resolve a problem without a test case 'on the
> >>> bench.'
> >>> We developers would like to turn over a bit of a new leaf. We're
> >>> going
> >>> to ask you to supply a test case to go with your bug reports. In
> >>> return, we're going to try very hard to attend to them. You can tar
> >>> it
> >>> up and attach it to the jira, or just push it to github and add a
> >>> link.
> >>>
> >>> To clean up the current mess, we plan to start going through the
> >>> backlog. We'll add comments asking for test cases or other followup.
> >>> If we don't hear back in two weeks, we're going to close.
> >>>
> >>> We're sorry for any frustration felt by the originators of
> >>> long-neglected reports, but we believe that this process will help
> >>> us
> >>> be more responsive in the future.
> >>>
> >>> --snip--
> >>>
> >>>
> >>> On Sat, Jun 18, 2011 at 7:22 PM, Stephen Connolly
> >>>
> >>> <[hidden email]> wrote:
> >>>> they can always reopen if they want after the issue has been
> >>>> closed if the 2nd weeks was too short
> >>>>
> >>>> - Stephen
> >>>>
> >>>> ---
> >>>> Sent from my Android phone, so random spelling mistakes, random
> >>>> nonsense words and other nonsense are a direct result of using
> >>>> swype to type on the screen
> >>>> On 19 Jun 2011 00:20, "Stephen
> >>>> Connolly"<[hidden email]>
> >>>>
> >>>> wrote:
> >>>>> +50
> >>>>>
> >>>>> I say lets give each issue a ping, wait 2 weeks and close if no
> >>>>> response
> >>>>>
> >>>>> - Stephen
> >>>>>
> >>>>> ---
> >>>>> Sent from my Android phone, so random spelling mistakes, random
> >>>>> nonsense words and other nonsense are a direct result of using
> >>>>> swype to type on the screen
> >>>>>
> >>>>> On 18 Jun 2011 23:30, "Benson Margulies"<[hidden email]>  
wrote:

> >>>>>> I just looked at the 'blocker' issues. We have a variety of
> >>>>>> very old
> >>>>>> JIRAs here. None of the ones I looked at have a self-contained
> >>>>>> test
> >>>>>> case that would can be downloaded, run, and converted to an
> >>>>>> integration test, etc.
> >>>>>>
> >>>>>> What's the policy? My temptation would be to comment on them
> >>>>>> asking if the OP is still interested (in some cases, 5 years
> >>>>>> later), and, if so, can they come up with a repeatable test
> >>>>>> case, and if not close as not a real bug.
> >>>>>>
> >>>>>> I don't mind in some cases doing work to build a test case,
> >>>>>> but to go to all this trouble for a bug that was opened about
> >>>>>> maven 2.0.x, where it may not be that easy to reconstruct the
> >>>>>> critical components of the problem, seems a dubious use of
> >>>>>> time.
> >>>>>>
> >>>>>> --------------------------------------------------------------
> >>>>>> ------- To unsubscribe, e-mail:
> >>>>>> [hidden email]
> >>>>>> For additional commands, e-mail: [hidden email]
> >>>
> >>> --------------------------------------------------------------------
> >>> -
> >>> To unsubscribe, e-mail: [hidden email]
> >>> For additional commands, e-mail: [hidden email]
> >>
> >> --
> >> John Casey
> >> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> >> Blog: http://www.johnofalltrades.name/
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
--
Daniel Kulp
[hidden email]
http://dankulp.com/blog
Talend - http://www.talend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The JIRA chocolate box

Benson Margulies
labels seems reasonable, assuming that Codehaus deploys them.

Given the positive response to this idea, I plan to send the email
tomorrow some time and start on MNG.



On Sun, Jun 19, 2011 at 3:24 PM, Daniel Kulp <[hidden email]> wrote:

> On Sunday, June 19, 2011 7:13:11 PM Dennis Lundberg wrote:
>> On 2011-06-19 18:46, Kristian Rosenvold wrote:
>> > Is there any smart way to tag a bug as processed in a triaging process
>> > so we can focus on the remaining bugs?
>> >
>> > I've always wondered if there's any option to tag an issue or create
>> > shared custom lists...?
>>
>> We should be able to use "Labels" for this:
>> http://confluence.atlassian.com/display/JIRA043/Labelling+an+Issue
>>
>> I haven't used them myself yet, but they seem to fit the bill.
>
> For CXF, we have a special "NeedMoreInfo" version that we use for this.   We
> set the "FixFor" version to that when we've added a comment that requires more
> information from the user.   We can easily get a list of all the issues that
> require more information, when we asked for it, etc.....
>
> Probably an abuse of the version field though.   :-)
>
> Dan
>
>
>>
>> > K
>> >
>> > Den 19. juni 2011 kl. 18:42 skrev John Casey <[hidden email]>:
>> >> +1
>> >>
>> >> Great idea!
>> >>
>> >> On 6/18/11 10:22 PM, Benson Margulies wrote:
>> >>> If no one objects to this idea, I'd like to add a component, which
>> >>> is
>> >>> an email like the following to the user list.
>> >>>
>> >>> --snip--
>> >>>
>> >>> Dear Maven Users,
>> >>>
>> >>> Over the years, the JIRA for core Maven
>> >>> (http://jira.codehaus.org/browse/MNG) has accumulated many
>> >>> unresolved
>> >>> issues. All this clutter makes it difficult to tell where the real
>> >>> problems are. Further, many of these issues do not contain
>> >>> self-contained test cases. Practically speaking, it is very
>> >>> difficult
>> >>> to diagnose and resolve a problem without a test case 'on the
>> >>> bench.'
>> >>> We developers would like to turn over a bit of a new leaf. We're
>> >>> going
>> >>> to ask you to supply a test case to go with your bug reports. In
>> >>> return, we're going to try very hard to attend to them. You can tar
>> >>> it
>> >>> up and attach it to the jira, or just push it to github and add a
>> >>> link.
>> >>>
>> >>> To clean up the current mess, we plan to start going through the
>> >>> backlog. We'll add comments asking for test cases or other followup.
>> >>> If we don't hear back in two weeks, we're going to close.
>> >>>
>> >>> We're sorry for any frustration felt by the originators of
>> >>> long-neglected reports, but we believe that this process will help
>> >>> us
>> >>> be more responsive in the future.
>> >>>
>> >>> --snip--
>> >>>
>> >>>
>> >>> On Sat, Jun 18, 2011 at 7:22 PM, Stephen Connolly
>> >>>
>> >>> <[hidden email]> wrote:
>> >>>> they can always reopen if they want after the issue has been
>> >>>> closed if the 2nd weeks was too short
>> >>>>
>> >>>> - Stephen
>> >>>>
>> >>>> ---
>> >>>> Sent from my Android phone, so random spelling mistakes, random
>> >>>> nonsense words and other nonsense are a direct result of using
>> >>>> swype to type on the screen
>> >>>> On 19 Jun 2011 00:20, "Stephen
>> >>>> Connolly"<[hidden email]>
>> >>>>
>> >>>> wrote:
>> >>>>> +50
>> >>>>>
>> >>>>> I say lets give each issue a ping, wait 2 weeks and close if no
>> >>>>> response
>> >>>>>
>> >>>>> - Stephen
>> >>>>>
>> >>>>> ---
>> >>>>> Sent from my Android phone, so random spelling mistakes, random
>> >>>>> nonsense words and other nonsense are a direct result of using
>> >>>>> swype to type on the screen
>> >>>>>
>> >>>>> On 18 Jun 2011 23:30, "Benson Margulies"<[hidden email]>
> wrote:
>> >>>>>> I just looked at the 'blocker' issues. We have a variety of
>> >>>>>> very old
>> >>>>>> JIRAs here. None of the ones I looked at have a self-contained
>> >>>>>> test
>> >>>>>> case that would can be downloaded, run, and converted to an
>> >>>>>> integration test, etc.
>> >>>>>>
>> >>>>>> What's the policy? My temptation would be to comment on them
>> >>>>>> asking if the OP is still interested (in some cases, 5 years
>> >>>>>> later), and, if so, can they come up with a repeatable test
>> >>>>>> case, and if not close as not a real bug.
>> >>>>>>
>> >>>>>> I don't mind in some cases doing work to build a test case,
>> >>>>>> but to go to all this trouble for a bug that was opened about
>> >>>>>> maven 2.0.x, where it may not be that easy to reconstruct the
>> >>>>>> critical components of the problem, seems a dubious use of
>> >>>>>> time.
>> >>>>>>
>> >>>>>> --------------------------------------------------------------
>> >>>>>> ------- To unsubscribe, e-mail:
>> >>>>>> [hidden email]
>> >>>>>> For additional commands, e-mail: [hidden email]
>> >>>
>> >>> --------------------------------------------------------------------
>> >>> -
>> >>> To unsubscribe, e-mail: [hidden email]
>> >>> For additional commands, e-mail: [hidden email]
>> >>
>> >> --
>> >> John Casey
>> >> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> >> Blog: http://www.johnofalltrades.name/
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [hidden email]
>> >> For additional commands, e-mail: [hidden email]
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [hidden email]
>> > For additional commands, e-mail: [hidden email]
> --
> Daniel Kulp
> [hidden email]
> http://dankulp.com/blog
> Talend - http://www.talend.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

12