You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Keith Turner <ke...@deenlo.com> on 2013/10/29 17:32:49 UTC
Discussion on JIRA
I saw someone posted the following link on HBASE ticket and I thought it
was interesting. I have participated and instigated long discussions on
tickets that do not quickly converge. It may be better if we moved these
to the mailing list as the link suggest.
http://producingoss.com/en/bug-tracker-usage.html
It would be nice to go to a ticket related a new 1.6.0 feature a year from
now, read it, and get a clear understanding of what transpired (rather than
be totally confused :).
Keith
Re: Discussion on JIRA
Posted by Josh Elser <jo...@gmail.com>.
+1 :D
On 10/29/13, 1:13 PM, Ted Yu wrote:
> One upside to discussion on mailing list is that it is immune to
> 'Maintenance in progress' of JIRA which is ongoing at the moment.
>
>
> On Tue, Oct 29, 2013 at 10:06 AM, Keith Turner <ke...@deenlo.com> wrote:
>
>> On Tue, Oct 29, 2013 at 12:50 PM, Josh Elser <jo...@gmail.com> wrote:
>>
>>> I think it heavily depends on the quality and focus of the discussion.
>>>
>>> Like you said, if the conversation is focused, it's nice to have the
>>> complete conversation present on that ticket.
>>>
>>
>> Well, the article said "...if the information looks like it will be quickly
>> convergent, then put it directly in the bug tracker; if it looks like it
>> will be divergent, then a mailing...".
>>
>>
>>>
>>> However, very often, we all get sidetracked and start talking about 8
>>> other things instead of what the ticket is actually about.
>>>
>>> Perhaps a good middle ground would be to move discussion to the mailing
>>> list when it gets off topic, and when the discussion comes to some
>>> consensus post back to the ticket with the link from mail-archives and a
>>> general synopsis with what was agreed upon?
>>
>>
>> I am not really sure at this point. Seems like a good bit of advice we can
>> take into consideration as we go forward..
>>
>>
>>>
>>>
>>> On 10/29/13, 12:32 PM, Keith Turner wrote:
>>>
>>>> I saw someone posted the following link on HBASE ticket and I thought it
>>>> was interesting. I have participated and instigated long discussions on
>>>> tickets that do not quickly converge. It may be better if we moved
>> these
>>>> to the mailing list as the link suggest.
>>>>
>>>> http://producingoss.com/en/**bug-tracker-usage.html<
>> http://producingoss.com/en/bug-tracker-usage.html>
>>>>
>>>> It would be nice to go to a ticket related a new 1.6.0 feature a year
>> from
>>>> now, read it, and get a clear understanding of what transpired (rather
>>>> than
>>>> be totally confused :).
>>>>
>>>> Keith
>>>>
>>>>
>>
>
Re: Discussion on JIRA
Posted by Ted Yu <yu...@gmail.com>.
One upside to discussion on mailing list is that it is immune to
'Maintenance in progress' of JIRA which is ongoing at the moment.
On Tue, Oct 29, 2013 at 10:06 AM, Keith Turner <ke...@deenlo.com> wrote:
> On Tue, Oct 29, 2013 at 12:50 PM, Josh Elser <jo...@gmail.com> wrote:
>
> > I think it heavily depends on the quality and focus of the discussion.
> >
> > Like you said, if the conversation is focused, it's nice to have the
> > complete conversation present on that ticket.
> >
>
> Well, the article said "...if the information looks like it will be quickly
> convergent, then put it directly in the bug tracker; if it looks like it
> will be divergent, then a mailing...".
>
>
> >
> > However, very often, we all get sidetracked and start talking about 8
> > other things instead of what the ticket is actually about.
> >
> > Perhaps a good middle ground would be to move discussion to the mailing
> > list when it gets off topic, and when the discussion comes to some
> > consensus post back to the ticket with the link from mail-archives and a
> > general synopsis with what was agreed upon?
>
>
> I am not really sure at this point. Seems like a good bit of advice we can
> take into consideration as we go forward..
>
>
> >
> >
> > On 10/29/13, 12:32 PM, Keith Turner wrote:
> >
> >> I saw someone posted the following link on HBASE ticket and I thought it
> >> was interesting. I have participated and instigated long discussions on
> >> tickets that do not quickly converge. It may be better if we moved
> these
> >> to the mailing list as the link suggest.
> >>
> >> http://producingoss.com/en/**bug-tracker-usage.html<
> http://producingoss.com/en/bug-tracker-usage.html>
> >>
> >> It would be nice to go to a ticket related a new 1.6.0 feature a year
> from
> >> now, read it, and get a clear understanding of what transpired (rather
> >> than
> >> be totally confused :).
> >>
> >> Keith
> >>
> >>
>
Re: Discussion on JIRA
Posted by Keith Turner <ke...@deenlo.com>.
On Tue, Oct 29, 2013 at 12:50 PM, Josh Elser <jo...@gmail.com> wrote:
> I think it heavily depends on the quality and focus of the discussion.
>
> Like you said, if the conversation is focused, it's nice to have the
> complete conversation present on that ticket.
>
Well, the article said "...if the information looks like it will be quickly
convergent, then put it directly in the bug tracker; if it looks like it
will be divergent, then a mailing...".
>
> However, very often, we all get sidetracked and start talking about 8
> other things instead of what the ticket is actually about.
>
> Perhaps a good middle ground would be to move discussion to the mailing
> list when it gets off topic, and when the discussion comes to some
> consensus post back to the ticket with the link from mail-archives and a
> general synopsis with what was agreed upon?
I am not really sure at this point. Seems like a good bit of advice we can
take into consideration as we go forward..
>
>
> On 10/29/13, 12:32 PM, Keith Turner wrote:
>
>> I saw someone posted the following link on HBASE ticket and I thought it
>> was interesting. I have participated and instigated long discussions on
>> tickets that do not quickly converge. It may be better if we moved these
>> to the mailing list as the link suggest.
>>
>> http://producingoss.com/en/**bug-tracker-usage.html<http://producingoss.com/en/bug-tracker-usage.html>
>>
>> It would be nice to go to a ticket related a new 1.6.0 feature a year from
>> now, read it, and get a clear understanding of what transpired (rather
>> than
>> be totally confused :).
>>
>> Keith
>>
>>
Re: Discussion on JIRA
Posted by Josh Elser <jo...@gmail.com>.
I think it heavily depends on the quality and focus of the discussion.
Like you said, if the conversation is focused, it's nice to have the
complete conversation present on that ticket.
However, very often, we all get sidetracked and start talking about 8
other things instead of what the ticket is actually about.
Perhaps a good middle ground would be to move discussion to the mailing
list when it gets off topic, and when the discussion comes to some
consensus post back to the ticket with the link from mail-archives and a
general synopsis with what was agreed upon?
On 10/29/13, 12:32 PM, Keith Turner wrote:
> I saw someone posted the following link on HBASE ticket and I thought it
> was interesting. I have participated and instigated long discussions on
> tickets that do not quickly converge. It may be better if we moved these
> to the mailing list as the link suggest.
>
> http://producingoss.com/en/bug-tracker-usage.html
>
> It would be nice to go to a ticket related a new 1.6.0 feature a year from
> now, read it, and get a clear understanding of what transpired (rather than
> be totally confused :).
>
> Keith
>
Re: Discussion on JIRA
Posted by Christopher <ct...@apache.org>.
Keep in mind also that conversations on bugs also go to the
notifications mailing list.
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Tue, Oct 29, 2013 at 12:32 PM, Keith Turner <ke...@deenlo.com> wrote:
> I saw someone posted the following link on HBASE ticket and I thought it
> was interesting. I have participated and instigated long discussions on
> tickets that do not quickly converge. It may be better if we moved these
> to the mailing list as the link suggest.
>
> http://producingoss.com/en/bug-tracker-usage.html
>
> It would be nice to go to a ticket related a new 1.6.0 feature a year from
> now, read it, and get a clear understanding of what transpired (rather than
> be totally confused :).
>
> Keith