[email protected] has been created, we can now move the noise from JIRA to it. PMC can make the changes as needed. I can take care of this as Needed.
@rawkintrevo, it is more convenient for you to wait until after to wait until after the release for the move of JIRA noise? ________________________________ From: Andrew Palumbo <[email protected]> Sent: Tuesday, June 27, 2017 8:11:52 PM To: [email protected] Subject: Re: [DISCUSS] New mailing list for JIRA requested that [email protected] be created so that we may point jira to email to it. ________________________________ From: Andrew Palumbo <[email protected]> Sent: Monday, June 26, 2017 5:32:09 PM To: [email protected] Subject: Re: [DISCUSS] New mailing list for JIRA I'll talk to/file with INFRA later to see if we can get this done. ________________________________ From: dustin vanstee <[email protected]> Sent: Monday, June 26, 2017 3:58:29 PM To: [email protected] Subject: Re: [DISCUSS] New mailing list for JIRA +1, it would really clean things up. On Mon, Jun 26, 2017 at 2:55 PM, Trevor Grant <[email protected]> wrote: > precedence : https://commons.apache.org/mail-lists.html > > (commits and notifications) > > that's 3 +1s. Lazy consensus if no one objects in the next 72 hours. > > > > > On Mon, Jun 26, 2017 at 1:47 PM, Andrew Palumbo <[email protected]> > wrote: > > > +1 > > > > > > if there is ASF precedence. > > > > ________________________________ > > From: Pat Ferrel <[email protected]> > > Sent: Monday, June 26, 2017 1:40:36 PM > > To: [email protected] > > Subject: Re: [DISCUSS] New mailing list for JIRA > > > > Other project I’ve seen funnel all github, Jira, and Jenkins emails to > one > > place so actual discussions are easier to notice in @dev > > +1 to moving elsewhere > > > > > > On Jun 24, 2017, at 5:23 AM, Trevor Grant <[email protected]> > > wrote: > > > > Can we create a new mailing list like [email protected] for all > this > > jira stuff? > > > > Any reason it needs to go to dev? > > > > >
