You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Jeff Jirsa <jj...@apache.org> on 2017/03/24 17:59:24 UTC
[RESULT][VOTE] Ask Infra to move github notification emails to pr@
With 6 binding +1s, 6 non-binding +1s, and no -1s of any kind, the vote passes, I'll ask for a new mailing list and get this transitioned.
- Jeff
On 2017-03-20 15:32 (-0700), Jeff Jirsa <jj...@gmail.com> wrote:
> There's no reason for the dev list to get spammed everytime there's a
> github PR. We know most of the time we prefer JIRAs for real code PRs, but
> with docs being in tree and low barrier to entry, we may want to accept
> docs through PRs ( see https://issues.apache.org/jira/browse/CASSANDRA-13256
> , and comment on it if you disagree).
>
> To make that viable, we should make it not spam dev@ with every comment.
> Therefore I propose we move github PR comments/actions to pr@ so as
> not to clutter the dev@ list.
>
> Voting to remain open for 72 hours.
>
> - Jeff
>
Re: [RESULT][VOTE] Ask Infra to move github notification emails to pr@
Posted by Jeff Jirsa <jj...@gmail.com>.
I'll open an infra ticket.
--
Jeff Jirsa
> On Jul 28, 2017, at 7:28 AM, Aleksey Yeschenko <al...@apache.org> wrote:
>
> +1
>
> —
> AY
>
> On 28 July 2017 at 11:47:29, Stefan Podkowinski (spod@apache.org) wrote:
>
> Can we forward notifications for the new cassandra-dtest repo there as well?
>
>> On 24.03.2017 18:59, Jeff Jirsa wrote:
>> With 6 binding +1s, 6 non-binding +1s, and no -1s of any kind, the vote passes, I'll ask for a new mailing list and get this transitioned.
>>
>> - Jeff
>>
>>> On 2017-03-20 15:32 (-0700), Jeff Jirsa <jj...@gmail.com> wrote:
>>> There's no reason for the dev list to get spammed everytime there's a
>>> github PR. We know most of the time we prefer JIRAs for real code PRs, but
>>> with docs being in tree and low barrier to entry, we may want to accept
>>> docs through PRs ( see https://issues.apache.org/jira/browse/CASSANDRA-13256
>>> , and comment on it if you disagree).
>>>
>>> To make that viable, we should make it not spam dev@ with every comment.
>>> Therefore I propose we move github PR comments/actions to pr@ so as
>>> not to clutter the dev@ list.
>>>
>>> Voting to remain open for 72 hours.
>>>
>>> - Jeff
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [RESULT][VOTE] Ask Infra to move github notification emails
to pr@
Posted by Aleksey Yeschenko <al...@apache.org>.
+1
—
AY
On 28 July 2017 at 11:47:29, Stefan Podkowinski (spod@apache.org) wrote:
Can we forward notifications for the new cassandra-dtest repo there as well?
On 24.03.2017 18:59, Jeff Jirsa wrote:
> With 6 binding +1s, 6 non-binding +1s, and no -1s of any kind, the vote passes, I'll ask for a new mailing list and get this transitioned.
>
> - Jeff
>
> On 2017-03-20 15:32 (-0700), Jeff Jirsa <jj...@gmail.com> wrote:
>> There's no reason for the dev list to get spammed everytime there's a
>> github PR. We know most of the time we prefer JIRAs for real code PRs, but
>> with docs being in tree and low barrier to entry, we may want to accept
>> docs through PRs ( see https://issues.apache.org/jira/browse/CASSANDRA-13256
>> , and comment on it if you disagree).
>>
>> To make that viable, we should make it not spam dev@ with every comment.
>> Therefore I propose we move github PR comments/actions to pr@ so as
>> not to clutter the dev@ list.
>>
>> Voting to remain open for 72 hours.
>>
>> - Jeff
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [RESULT][VOTE] Ask Infra to move github notification emails to
pr@
Posted by Stefan Podkowinski <sp...@apache.org>.
Can we forward notifications for the new cassandra-dtest repo there as well?
On 24.03.2017 18:59, Jeff Jirsa wrote:
> With 6 binding +1s, 6 non-binding +1s, and no -1s of any kind, the vote passes, I'll ask for a new mailing list and get this transitioned.
>
> - Jeff
>
> On 2017-03-20 15:32 (-0700), Jeff Jirsa <jj...@gmail.com> wrote:
>> There's no reason for the dev list to get spammed everytime there's a
>> github PR. We know most of the time we prefer JIRAs for real code PRs, but
>> with docs being in tree and low barrier to entry, we may want to accept
>> docs through PRs ( see https://issues.apache.org/jira/browse/CASSANDRA-13256
>> , and comment on it if you disagree).
>>
>> To make that viable, we should make it not spam dev@ with every comment.
>> Therefore I propose we move github PR comments/actions to pr@ so as
>> not to clutter the dev@ list.
>>
>> Voting to remain open for 72 hours.
>>
>> - Jeff
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org