Thanks for everyone who has spoken out. I have filed
https://issues.apache.org/jira/browse/INFRA-14336
to Apache INFRA.
Guozhang
On Fri, Jun 9, 2017 at 3:07 PM, Matthias J. Sax
wrote:
> +1
>
> On 6/9/17 3:01 PM, Bill Bejeck wrote:
> > +1
> >
> > Thanks,
> > Bill
> >
> > On Fri, Jun 9, 2017 at
+1
On 6/9/17 3:01 PM, Bill Bejeck wrote:
> +1
>
> Thanks,
> Bill
>
> On Fri, Jun 9, 2017 at 4:56 PM, Gwen Shapira wrote:
>
>> +1, thank you
>>
>> On Fri, Jun 9, 2017 at 1:37 PM Jeff Widman wrote:
>>
>>> +1
>>>
>>> Thanks for driving this
>>>
>>> On Jun 9, 2017 1:22 PM, "Guozhang Wang" wrote:
+1
Thanks,
Bill
On Fri, Jun 9, 2017 at 4:56 PM, Gwen Shapira wrote:
> +1, thank you
>
> On Fri, Jun 9, 2017 at 1:37 PM Jeff Widman wrote:
>
> > +1
> >
> > Thanks for driving this
> >
> > On Jun 9, 2017 1:22 PM, "Guozhang Wang" wrote:
> >
> > > I have just confirmed with Jun that de cannot cha
+1, thank you
On Fri, Jun 9, 2017 at 1:37 PM Jeff Widman wrote:
> +1
>
> Thanks for driving this
>
> On Jun 9, 2017 1:22 PM, "Guozhang Wang" wrote:
>
> > I have just confirmed with Jun that de cannot change the notification
> edits
> > himself as well. So I'll talk to Apache Infra anyways in or
+1
Thanks for driving this
On Jun 9, 2017 1:22 PM, "Guozhang Wang" wrote:
> I have just confirmed with Jun that de cannot change the notification edits
> himself as well. So I'll talk to Apache Infra anyways in order to make that
> change.
>
> So I'd update my proposal to:
>
> 1. create an "iss
I have just confirmed with Jun that de cannot change the notification edits
himself as well. So I'll talk to Apache Infra anyways in order to make that
change.
So I'd update my proposal to:
1. create an "iss...@kafka.apache.org" which will receive all the JIRA
events.
2. remove "dev@kafka.apache.
Yeah I have thought about that but that would involve Apache Infra. The
current proposal is based on the assumption that removing the notification
can be done by ourselves.
Guozhang
On Wed, Jun 7, 2017 at 1:24 PM, Matthias J. Sax
wrote:
> Have you considered starting a new mailing list "issues
Have you considered starting a new mailing list "issues@" that gets the
full load of all emails?
-Matthias
On 6/6/17 7:26 PM, Jeff Widman wrote:
> What about also adding "Issue Resolved" to the events that hit dev?
>
> While I don't generally care about updates on issue progress, I do want to
>
What about also adding "Issue Resolved" to the events that hit dev?
While I don't generally care about updates on issue progress, I do want to
know when issues are resolved in case undocumented behavior that I may have
accidentally been relying on may have changed.
With or without this suggested
Agree on proposal.
On Tue, Jun 6, 2017 at 3:55 PM Guozhang Wang wrote:
> Just clarifying: currently all events are notified to the following
> recipients:
>
> All Watchers
> Current Assignee
> Reporter
> Single Email Address (dev@kafka.apache.org)
>
>
> So by removing the last one, other related
Just clarifying: currently all events are notified to the following
recipients:
All Watchers
Current Assignee
Reporter
Single Email Address (dev@kafka.apache.org)
So by removing the last one, other related people (watcher, assignee,
reporter) will still be notified.
Guozhang
On Tue, Jun 6,
(Changing the subject title to reflect on the proposal)
Hey guys,
In order to not drop the ball on the floor I'd like to kick off some
proposals according to people's feedbacks on this issue. Feel free to
brainstorm on different ideas:
We change JIRA notifications to remove `Single Email Address
12 matches
Mail list logo
