On Tue, Oct 27, 2015 at 8:25 PM, Marvin Humphrey <[email protected]> wrote:
> On Tue, Oct 27, 2015 at 6:12 PM, Justin Mclean <[email protected]> > wrote: > > Hi, > > > >> Hi, sorry I didn't catch this earlier, but the original plan was to > have all > >> notifications including JIRA to be sent to notifications@mynewt. > > > > Isn’t that normally for notifications rather than issues? i.e. We can > keep > > both use issues for JIRA and notifications for release announcement and > the > > like? > > Take a look at this page and click on links named "notifications" or > "announce": > > http://mail-archives.apache.org/mod_mbox > > If this project had an announcement list it would probably be named > "announce@mynewt". But the project is not big enough right now to need > such a > list. > > The "notifications@" list is usually used for CI. It sometimes also gets > issue tracker notifications. > > The list name itself isn't really a big deal. The critical choices are: > > 1. Keep all that autogenerated mail off the dev list so the > signal-to-noise > ratio stays high. > 2. Put all the autogenerated mail except commits on *one* list instead of > several. It's all for core devs anyhow. > For the record, I'm with Marvin on this: fewer lists. I filed the mailing list creations, but felt it wasn't my place to question them at the time. ... I'm glad this discussion is here. (yes, Marvin fired that ticket awfully quick, but nothing is permanent) Cheers, -g
