+1 for new JIRA issues -1 for MTCGA notifications Why we should hide errors from the dev-list? Who should take care of issues reported by MTCGA.Bot in this case? We must apply stricter rules for such issues: a commit leading to an error must be reverted.
On Wed, 14 Apr 2021 at 20:00, Denis Mekhanikov <dmekhani...@gmail.com> wrote: > > Huge +1 to this. > > I've already brought up this topic in the past: > http://apache-ignite-developers.2346864.n4.nabble.com/Bots-on-dev-list-td34406.html > I hope some day newcomers won't need to set up their email filters when > they come to the developers list. > > Denis > > ср, 14 апр. 2021 г. в 18:07, Atri Sharma <a...@apache.org>: > > > +1 to move issues to the issues list. > > > > For MTCGA, maybe build@? > > > > On Wed, Apr 14, 2021 at 8:35 PM Ilya Kasnacheev <il...@apache.org> wrote: > > > > > > Hello! > > > > > > We have a discussion on how to ensure best engagement in dev@ list, and > > it > > > seems that Issue Created emails from IGNITE project consume a lot of > > screen > > > space, it's hard to spot genuine discussions in > > > https://lists.apache.org/list.html?dev@ignite.apache.org for example. > > > > > > We already have issues@ mailing list. I propose that we stop sending any > > > JIRA emails to dev@. If anyone wishes to get just Created emails, they > > can > > > subscribe to these messages in their JIRA account settings. I imagine > > most > > > of you already filter these messages out, so you may need to adjust your > > > filters slightly. > > > > > > A distant second is MTCGA messages, which are also autogenerated and not > > > informative for most readers of the channel, since they are at best > > > targeted at a single committer and at worst flaky. > > > > > > Where could we move those? What is your opinion here, on both issues? > > > > > > Regards, > > > > -- > > Regards, > > > > Atri > > Apache Concerted > >
