htrace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Elliott Clark <ecl...@apache.org>
Subject Re: Created/Resolved JIRA actions to dev list?
Date Sat, 03 Jan 2015 01:03:35 GMT
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 <cmccabe@alumni.cmu.edu>
wrote:

> +1.
>
> Colin
>
> On Fri, Dec 19, 2014 at 11:12 AM, Andrew Purtell <apurtell@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" <jfarrell@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 <ndimiduk@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)
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message