https://bugzilla.redhat.com/show_bug.cgi?id=1584998
Worker Ant changed:
What|Removed |Added
Status|NEW |CLOSED
Resolution|---
https://bugzilla.redhat.com/show_bug.cgi?id=1584998
Amar Tumballi changed:
What|Removed |Added
Priority|unspecified |low
Status|ASSIGNED
https://bugzilla.redhat.com/show_bug.cgi?id=1584998
PnT Account Manager changed:
What|Removed |Added
Assignee|nig...@redhat.com |b...@gluster.org
--
You are re
https://bugzilla.redhat.com/show_bug.cgi?id=1584998
--- Comment #9 from Niels de Vos ---
(In reply to Shyamsundar from comment #7)
> This is more for fly-by and/or folks who want to add reviewers clearly to
> call to attention the patch submitted.
Ideally this should not be needed. However I a
https://bugzilla.redhat.com/show_bug.cgi?id=1584998
--- Comment #8 from Nigel Babu ---
Alright, so let me put down Shyam's suggestion into a good infra action:
Run a job in smoke which checks if the maintainers for the component are
already added. If yes, do nothing. If not, add them. If a pat
https://bugzilla.redhat.com/show_bug.cgi?id=1584998
Nigel Babu changed:
What|Removed |Added
Summary|need automatic inclusion of |Need automatic inclusion of
https://bugzilla.redhat.com/show_bug.cgi?id=1584998
--- Comment #7 from Shyamsundar ---
(In reply to Nigel Babu from comment #5)
> I'm going to be a bit skeptical here. If someone doesn't notice their first
> email notification, would an additional email actually help?
>
> Our recommendation i
https://bugzilla.redhat.com/show_bug.cgi?id=1584998
Niels de Vos changed:
What|Removed |Added
CC||nde...@redhat.com
--- Comment #6 from
https://bugzilla.redhat.com/show_bug.cgi?id=1584998
Nigel Babu changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://bugzilla.redhat.com/show_bug.cgi?id=1584998
--- Comment #4 from Shyamsundar ---
(In reply to Niels de Vos from comment #3)
> If reviewers are added automatically, but still no action is taken after ~2
> weeks, it may make sense to send an email with some details about the
> proposed cha
https://bugzilla.redhat.com/show_bug.cgi?id=1584998
--- Comment #3 from Niels de Vos ---
If reviewers are added automatically, but still no action is taken after ~2
weeks, it may make sense to send an email with some details about the proposed
change to the maintainers mailing list.
--
You ar
https://bugzilla.redhat.com/show_bug.cgi?id=1584998
--- Comment #2 from Shyamsundar ---
My thoughts:
Let's not do it after 2 weeks, let it happen as the review is posted.
Also, let's add MAINTAINERS as per their areas of responsibility, that way a
patch does not get 20 reviewers, but rather 2
https://bugzilla.redhat.com/show_bug.cgi?id=1584998
--- Comment #1 from Amar Tumballi ---
Notice that this has a problem that we can get into infinite loop of warning
people every 2weeks of inactivity, but never reaching 90days. Hence we need a
mechanism to identify the patches only once, ie, f
13 matches
Mail list logo