You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@htrace.apache.org by Nick Dimiduk <nd...@gmail.com> on 2014/12/16 23:59:38 UTC
Created/Resolved JIRA actions to dev list?
What does it take to setup the above? I like how HBase does it :)
Re: Created/Resolved JIRA actions to dev list?
Posted by Jake Farrell <jf...@apache.org>.
To edit the notification scheme you do need to be an admin, I can change it
if we want
-Jake
On Thu, Dec 18, 2014 at 4:39 PM, Stack <st...@duboce.net> wrote:
>
> HBase uses the 'Hadoop HBase notification'. See
>
> https://issues.apache.org/jira/plugins/servlet/project-config/HBASE/notifications
>
>
> HTrace uses 'HTrace Notifications Scheme':
>
> https://issues.apache.org/jira/plugins/servlet/project-config/HTRACE/notifications
>
> INFRA set is up for us though in the ticket, they said you don't need
> global admin to do it: https://issues.apache.org/jira/browse/INFRA-5698
>
> I don't seem to have necessary privileges to do it for htrace though.
>
> St.Ack
>
> On Tue, Dec 16, 2014 at 2:59 PM, Nick Dimiduk <nd...@gmail.com> wrote:
> >
> > What does it take to setup the above? I like how HBase does it :)
> >
>
Re: Created/Resolved JIRA actions to dev list?
Posted by Stack <st...@duboce.net>.
HBase uses the 'Hadoop HBase notification'. See
https://issues.apache.org/jira/plugins/servlet/project-config/HBASE/notifications
HTrace uses 'HTrace Notifications Scheme':
https://issues.apache.org/jira/plugins/servlet/project-config/HTRACE/notifications
INFRA set is up for us though in the ticket, they said you don't need
global admin to do it: https://issues.apache.org/jira/browse/INFRA-5698
I don't seem to have necessary privileges to do it for htrace though.
St.Ack
On Tue, Dec 16, 2014 at 2:59 PM, Nick Dimiduk <nd...@gmail.com> wrote:
>
> What does it take to setup the above? I like how HBase does it :)
>
Re: Created/Resolved JIRA actions to dev list?
Posted by Stack <st...@duboce.net>.
No need of vote I'd say.
Jake Farrell, can you change it? I can file an INFRA issue if needbe.
St.Ack
On Sun, Jan 4, 2015 at 12:03 PM, Colin McCabe <cm...@alumni.cmu.edu>
wrote:
> That's weird. issues@htrace.incubator.apache.org is sending stuff to me.
>
> I agree with Andrew and Nick that we should send "created" and
> "resolved" actions to the dev@ mailing list, that is very convenient.
> Should we have a vote on that?
>
> Colin
>
> On Fri, Jan 2, 2015 at 5:03 PM, Elliott Clark <ec...@apache.org> wrote:
> > I'm not getting anything from the issues@ mailing list. Is anyone else
> > seeing the same?
> >
> > On Fri, Dec 19, 2014 at 2:42 PM, Colin McCabe <cm...@alumni.cmu.edu>
> > wrote:
> >
> >> +1.
> >>
> >> Colin
> >>
> >> On Fri, Dec 19, 2014 at 11:12 AM, Andrew Purtell <ap...@apache.org>
> >> wrote:
> >> > When watching HBase and HDFS (and other Hadoop) JIRAs, I rely on their
> >> > configuration where create and resolution events are copied to dev@
> to
> >> > become aware of newly filed or resolved issues. Individual issues can
> be
> >> > watched. This is a great middle ground between nothing and an issues@
> >> list
> >> > flood. Please consider it for HTrace.
> >> >
> >> > On Wed, Dec 17, 2014 at 2:43 PM, Colin McCabe <cmccabe@alumni.cmu.edu
> >
> >> > wrote:
> >> >>
> >> >> I too am used to JIRAs going to the list. I've been sending both
> >> >> dev@htrace.incubator.apache.org and issues@ to the same gmail label
> to
> >> get
> >> >> that setup for myself. I would have no objection to merging the
> lists,
> >> >> although I don't feel strongly about it.
> >> >>
> >> >> Colin
> >> >> On Dec 16, 2014 6:08 PM, "Jake Farrell" <jf...@apache.org> wrote:
> >> >>
> >> >> > Right now its setup to send jira notifications to
> >> >> > issues@htrace.incubator.apache.org, this helps keep the dev list a
> >> >> little
> >> >> > cleaner and easier to follow. If everyone would like to switch and
> use
> >> >> the
> >> >> > dev list for all jira notices then we can change it
> >> >> >
> >> >> > -Jake
> >> >> >
> >> >> > On Tue, Dec 16, 2014 at 5:59 PM, Nick Dimiduk <nd...@gmail.com>
> >> >> wrote:
> >> >> > >
> >> >> > > What does it take to setup the above? I like how HBase does it :)
> >> >> > >
> >> >> >
> >> >>
> >> >
> >> >
> >> > --
> >> > Best regards,
> >> >
> >> > - Andy
> >> >
> >> > Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> >> > (via Tom White)
> >>
>
Re: Created/Resolved JIRA actions to dev list?
Posted by Colin McCabe <cm...@alumni.cmu.edu>.
That's weird. issues@htrace.incubator.apache.org is sending stuff to me.
I agree with Andrew and Nick that we should send "created" and
"resolved" actions to the dev@ mailing list, that is very convenient.
Should we have a vote on that?
Colin
On Fri, Jan 2, 2015 at 5:03 PM, Elliott Clark <ec...@apache.org> wrote:
> I'm not getting anything from the issues@ mailing list. Is anyone else
> seeing the same?
>
> On Fri, Dec 19, 2014 at 2:42 PM, Colin McCabe <cm...@alumni.cmu.edu>
> wrote:
>
>> +1.
>>
>> Colin
>>
>> On Fri, Dec 19, 2014 at 11:12 AM, Andrew Purtell <ap...@apache.org>
>> wrote:
>> > When watching HBase and HDFS (and other Hadoop) JIRAs, I rely on their
>> > configuration where create and resolution events are copied to dev@ to
>> > become aware of newly filed or resolved issues. Individual issues can be
>> > watched. This is a great middle ground between nothing and an issues@
>> list
>> > flood. Please consider it for HTrace.
>> >
>> > On Wed, Dec 17, 2014 at 2:43 PM, Colin McCabe <cm...@alumni.cmu.edu>
>> > wrote:
>> >>
>> >> I too am used to JIRAs going to the list. I've been sending both
>> >> dev@htrace.incubator.apache.org and issues@ to the same gmail label to
>> get
>> >> that setup for myself. I would have no objection to merging the lists,
>> >> although I don't feel strongly about it.
>> >>
>> >> Colin
>> >> On Dec 16, 2014 6:08 PM, "Jake Farrell" <jf...@apache.org> wrote:
>> >>
>> >> > Right now its setup to send jira notifications to
>> >> > issues@htrace.incubator.apache.org, this helps keep the dev list a
>> >> little
>> >> > cleaner and easier to follow. If everyone would like to switch and use
>> >> the
>> >> > dev list for all jira notices then we can change it
>> >> >
>> >> > -Jake
>> >> >
>> >> > On Tue, Dec 16, 2014 at 5:59 PM, Nick Dimiduk <nd...@gmail.com>
>> >> wrote:
>> >> > >
>> >> > > What does it take to setup the above? I like how HBase does it :)
>> >> > >
>> >> >
>> >>
>> >
>> >
>> > --
>> > Best regards,
>> >
>> > - Andy
>> >
>> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> > (via Tom White)
>>
Re: Created/Resolved JIRA actions to dev list?
Posted by Elliott Clark <ec...@apache.org>.
I'm not getting anything from the issues@ mailing list. Is anyone else
seeing the same?
On Fri, Dec 19, 2014 at 2:42 PM, Colin McCabe <cm...@alumni.cmu.edu>
wrote:
> +1.
>
> Colin
>
> On Fri, Dec 19, 2014 at 11:12 AM, Andrew Purtell <ap...@apache.org>
> wrote:
> > When watching HBase and HDFS (and other Hadoop) JIRAs, I rely on their
> > configuration where create and resolution events are copied to dev@ to
> > become aware of newly filed or resolved issues. Individual issues can be
> > watched. This is a great middle ground between nothing and an issues@
> list
> > flood. Please consider it for HTrace.
> >
> > On Wed, Dec 17, 2014 at 2:43 PM, Colin McCabe <cm...@alumni.cmu.edu>
> > wrote:
> >>
> >> I too am used to JIRAs going to the list. I've been sending both
> >> dev@htrace.incubator.apache.org and issues@ to the same gmail label to
> get
> >> that setup for myself. I would have no objection to merging the lists,
> >> although I don't feel strongly about it.
> >>
> >> Colin
> >> On Dec 16, 2014 6:08 PM, "Jake Farrell" <jf...@apache.org> wrote:
> >>
> >> > Right now its setup to send jira notifications to
> >> > issues@htrace.incubator.apache.org, this helps keep the dev list a
> >> little
> >> > cleaner and easier to follow. If everyone would like to switch and use
> >> the
> >> > dev list for all jira notices then we can change it
> >> >
> >> > -Jake
> >> >
> >> > On Tue, Dec 16, 2014 at 5:59 PM, Nick Dimiduk <nd...@gmail.com>
> >> wrote:
> >> > >
> >> > > What does it take to setup the above? I like how HBase does it :)
> >> > >
> >> >
> >>
> >
> >
> > --
> > Best regards,
> >
> > - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
>
Re: Created/Resolved JIRA actions to dev list?
Posted by Colin McCabe <cm...@alumni.cmu.edu>.
+1.
Colin
On Fri, Dec 19, 2014 at 11:12 AM, Andrew Purtell <ap...@apache.org> wrote:
> When watching HBase and HDFS (and other Hadoop) JIRAs, I rely on their
> configuration where create and resolution events are copied to dev@ to
> become aware of newly filed or resolved issues. Individual issues can be
> watched. This is a great middle ground between nothing and an issues@ list
> flood. Please consider it for HTrace.
>
> On Wed, Dec 17, 2014 at 2:43 PM, Colin McCabe <cm...@alumni.cmu.edu>
> wrote:
>>
>> I too am used to JIRAs going to the list. I've been sending both
>> dev@htrace.incubator.apache.org and issues@ to the same gmail label to get
>> that setup for myself. I would have no objection to merging the lists,
>> although I don't feel strongly about it.
>>
>> Colin
>> On Dec 16, 2014 6:08 PM, "Jake Farrell" <jf...@apache.org> wrote:
>>
>> > Right now its setup to send jira notifications to
>> > issues@htrace.incubator.apache.org, this helps keep the dev list a
>> little
>> > cleaner and easier to follow. If everyone would like to switch and use
>> the
>> > dev list for all jira notices then we can change it
>> >
>> > -Jake
>> >
>> > On Tue, Dec 16, 2014 at 5:59 PM, Nick Dimiduk <nd...@gmail.com>
>> wrote:
>> > >
>> > > What does it take to setup the above? I like how HBase does it :)
>> > >
>> >
>>
>
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
Re: Created/Resolved JIRA actions to dev list?
Posted by Andrew Purtell <ap...@apache.org>.
When watching HBase and HDFS (and other Hadoop) JIRAs, I rely on their
configuration where create and resolution events are copied to dev@ to
become aware of newly filed or resolved issues. Individual issues can be
watched. This is a great middle ground between nothing and an issues@ list
flood. Please consider it for HTrace.
On Wed, Dec 17, 2014 at 2:43 PM, Colin McCabe <cm...@alumni.cmu.edu>
wrote:
>
> I too am used to JIRAs going to the list. I've been sending both
> dev@htrace.incubator.apache.org and issues@ to the same gmail label to get
> that setup for myself. I would have no objection to merging the lists,
> although I don't feel strongly about it.
>
> Colin
> On Dec 16, 2014 6:08 PM, "Jake Farrell" <jf...@apache.org> wrote:
>
> > Right now its setup to send jira notifications to
> > issues@htrace.incubator.apache.org, this helps keep the dev list a
> little
> > cleaner and easier to follow. If everyone would like to switch and use
> the
> > dev list for all jira notices then we can change it
> >
> > -Jake
> >
> > On Tue, Dec 16, 2014 at 5:59 PM, Nick Dimiduk <nd...@gmail.com>
> wrote:
> > >
> > > What does it take to setup the above? I like how HBase does it :)
> > >
> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: Created/Resolved JIRA actions to dev list?
Posted by Nick Dimiduk <nd...@gmail.com>.
issues@ for this project should be pretty low traffic, so I'll just
subscribe there. When we become a higher volume project, maybe we can
reconsider.
On Wed, Dec 17, 2014 at 2:43 PM, Colin McCabe <cm...@alumni.cmu.edu>
wrote:
>
> I too am used to JIRAs going to the list. I've been sending both
> dev@htrace.incubator.apache.org and issues@ to the same gmail label to get
> that setup for myself. I would have no objection to merging the lists,
> although I don't feel strongly about it.
>
> Colin
> On Dec 16, 2014 6:08 PM, "Jake Farrell" <jf...@apache.org> wrote:
>
> > Right now its setup to send jira notifications to
> > issues@htrace.incubator.apache.org, this helps keep the dev list a
> little
> > cleaner and easier to follow. If everyone would like to switch and use
> the
> > dev list for all jira notices then we can change it
> >
> > -Jake
> >
> > On Tue, Dec 16, 2014 at 5:59 PM, Nick Dimiduk <nd...@gmail.com>
> wrote:
> > >
> > > What does it take to setup the above? I like how HBase does it :)
> > >
> >
>
Re: Created/Resolved JIRA actions to dev list?
Posted by Colin McCabe <cm...@alumni.cmu.edu>.
I too am used to JIRAs going to the list. I've been sending both
dev@htrace.incubator.apache.org and issues@ to the same gmail label to get
that setup for myself. I would have no objection to merging the lists,
although I don't feel strongly about it.
Colin
On Dec 16, 2014 6:08 PM, "Jake Farrell" <jf...@apache.org> wrote:
> Right now its setup to send jira notifications to
> issues@htrace.incubator.apache.org, this helps keep the dev list a little
> cleaner and easier to follow. If everyone would like to switch and use the
> dev list for all jira notices then we can change it
>
> -Jake
>
> On Tue, Dec 16, 2014 at 5:59 PM, Nick Dimiduk <nd...@gmail.com> wrote:
> >
> > What does it take to setup the above? I like how HBase does it :)
> >
>
Re: Created/Resolved JIRA actions to dev list?
Posted by Jake Farrell <jf...@apache.org>.
Right now its setup to send jira notifications to
issues@htrace.incubator.apache.org, this helps keep the dev list a little
cleaner and easier to follow. If everyone would like to switch and use the
dev list for all jira notices then we can change it
-Jake
On Tue, Dec 16, 2014 at 5:59 PM, Nick Dimiduk <nd...@gmail.com> wrote:
>
> What does it take to setup the above? I like how HBase does it :)
>