Hi Vladimir,
In general, I agree with these ideas, but it will be a lot of work to be
done to make personal notification even possible. We need to match each TC
and GitHub, GitHub account with email, this could become huge manual work.
We need to develop personal notifications code. Would you like
Folks,
If there will be a single thread for all failures, nobody will read it.
Simply because it will be always "unread", with tons of messages, where it
would be impossible to find a failure I am responsible for.
Several threads - on per suite - makes situation a bit better, but still
nobody will
Dmitriy,
I like your idea to add suite name.
On Mon, Sep 10, 2018 at 5:42 PM Dmitriy Pavlov
wrote:
> Hi Alexey,
>
> Thank you for that brilliant idea. Build ID was added intentionally to
> separate topics. But for timeout failures, it creates odd topics.
>
> I would like to suggest a modificat
Hi Alexey,
Thank you for that brilliant idea. Build ID was added intentionally to
separate topics. But for timeout failures, it creates odd topics.
I would like to suggest a modification of the idea: What if we will include
a suite name instead of build ID. It will keep the context of suite
failu
Dmitriy,
How about to change e-mail subject
from *[MTCGA]: new failures in builds [n] needs to be handled*
to *[MTCGA]: new failures in builds needs to be handled* ?
If subject will be the same it will not produce lots of threads on dev list
and it will be a single thread.
What do you think?
Hi everyone,
I think email from the bot is something exceptional. In this case author
and committer already ignored test failures. So dev list is the last hope
that someone can come and fix the failure.
Other emails come from human actions, so I'm happy that so many actions
occur in the community
> 2. MTCGA messages should mention the commiter and authors of the "bad"
commit.
But this is not always possible.
2018-08-30 13:04 GMT+03:00 Dmitrii Ryabov :
> Vladimir, your idea is good, but...
> 1. Who should be mentioned in messages like PR or JIRA ticket creation? As
> I see, only these mess
Vladimir, your idea is good, but...
1. Who should be mentioned in messages like PR or JIRA ticket creation? As
I see, only these messages clutter up the nabble.
2. MTCGA messages should mention the commiter and authors of the "bad"
commit.
2. Comments and changes in PR, tickets, and reviews already
Huge +1 for separate channel for bots and direct notification.
On Thu, Aug 30, 2018 at 12:20 PM Vladimir Ozerov
wrote:
> This is somewhat controversial question. Some people has filters, some
> doesn't. And it s true that at the moment it is hard to find pieces of
> human communication in tons o
This is somewhat controversial question. Some people has filters, some
doesn't. And it s true that at the moment it is hard to find pieces of
human communication in tons of automated e-mails (JIRA, GitHub, TC bot).
If to put JIRA and GitHub aside (let's do not mix things), personally
content of TC
I guess, nobody uses it because it's flooded by bots.
It may be useful to lookup old threads for people, who are not subscribed
to the mailing list from the beginning of time.
Denis
чт, 30 авг. 2018 г. в 3:39, Dmitriy Setrakyan :
> Is anyone in the community using or was using Nabble for the dev
Is anyone in the community using or was using Nabble for the dev list
communication? Personally, I am subscribed to the dev list and use filters
in my email client.
D.
On Wed, Aug 29, 2018 at 3:40 AM, Denis Mekhanikov
wrote:
> Guys,
>
> Yep, I use filters on my mail account. But the portal is i
Guys,
Yep, I use filters on my mail account. But the portal is impossible to use.
When you subscribe to the dev list for the first time, you don't have any
history on your email,
and the archive is polluted with messages, sent by bots.
Some view on Nabble, that doesn't contain any automatically g
Denis,
I am against filtering out MTCGA messages from the dev-list because test
failures affect every developer in the community and may be caused by any
developer in the community. Usually such emails require immediate action
and it would be wrong to move them to a separate list.
I understand, t
Denis,
I would like to keep a single entry point into the whole Ignite development
process project,
but maybe other Igniters have another opinion on this. As for me, it's a
more convenient way
for searching any activity on dev.list by single keyword (e.g. PRs, JIRAs,
topics).
As mentioned Dmitry,
Modern mail services allow users to filter messages. You can easily filter
out bot messages.
2018-08-29 11:48 GMT+03:00 Denis Mekhanikov :
> Igniters,
>
> We have a lot of threads, created by bots on the dev list.
> Currently messages are sent by JIRA, GitHub and MTCGA bots. Maybe, some
> others
Igniters,
We have a lot of threads, created by bots on the dev list.
Currently messages are sent by JIRA, GitHub and MTCGA bots. Maybe, some
others too, but these are the most active.
Take a look at this page:
http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-Developers-f1i35.ht
17 matches
Mail list logo
