Re: [RESULT][VOTE] Ask Infra to move github notification emails to pr@
I'll open an infra ticket. -- Jeff Jirsa > On Jul 28, 2017, at 7:28 AM, Aleksey Yeschenko wrote: > > +1 > > — > AY > > On 28 July 2017 at 11:47:29, Stefan Podkowinski (s...@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 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-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: [RESULT][VOTE] Ask Infra to move github notification emails to pr@
+1 — AY On 28 July 2017 at 11:47:29, Stefan Podkowinski (s...@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 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: [RESULT][VOTE] Ask Infra to move github notification emails to pr@
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 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
[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 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 >