That's weird. [email protected] 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 <[email protected]> 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 <[email protected]> > wrote: > >> +1. >> >> Colin >> >> On Fri, Dec 19, 2014 at 11:12 AM, Andrew Purtell <[email protected]> >> 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 <[email protected]> >> > wrote: >> >> >> >> I too am used to JIRAs going to the list. I've been sending both >> >> [email protected] 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" <[email protected]> wrote: >> >> >> >> > Right now its setup to send jira notifications to >> >> > [email protected], 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 <[email protected]> >> >> 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) >>
