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 >
Re: [VOTE] Ask Infra to move github notification emails to pr@
+1 2017-03-20 21:28 GMT-07:00 Amitkumar Ghatwal : > +1 > > [image: Inactive hide details for Michael Shuler ---03/21/2017 08:59:43 > AM---+1 On 03/20/2017 05:32 PM, Jeff Jirsa wrote:]Michael Shuler > ---03/21/2017 08:59:43 AM---+1 On 03/20/2017 05:32 PM, Jeff Jirsa wrote: > > From: Michael Shuler > To: dev@cassandra.apache.org > Date: 03/21/2017 08:59 AM > Subject: Re: [VOTE] Ask Infra to move github notification emails to pr@ > Sent by: Michael Shuler > -- > > > > +1 > > On 03/20/2017 05:32 PM, 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 > > > > > > >
Re: [VOTE] Ask Infra to move github notification emails to pr@
+1 From: Michael Shuler To: dev@cassandra.apache.org Date: 03/21/2017 08:59 AM Subject:Re: [VOTE] Ask Infra to move github notification emails to pr@ Sent by:Michael Shuler +1 On 03/20/2017 05:32 PM, 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 >
Re: [VOTE] Ask Infra to move github notification emails to pr@
+1 On 03/20/2017 05:32 PM, 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 >
Re: [VOTE] Ask Infra to move github notification emails to pr@
+1 On Mon, Mar 20, 2017 at 8:26 PM, jason zhao yang < zhaoyangsingap...@gmail.com> wrote: > +1 > On Tue, 21 Mar 2017 at 9:36 AM, Jonathan Haddad wrote: > > > +1 > > On Mon, Mar 20, 2017 at 6:33 PM Jason Brown > wrote: > > > > > +1 > > > On Mon, Mar 20, 2017 at 18:21 Anthony Grasso > > > > wrote: > > > > > > > +1 > > > > > > > > On 21 March 2017 at 09:32, 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 > > > > > > > > > > > > > > >
Re: [VOTE] Ask Infra to move github notification emails to pr@
+1 On Tue, 21 Mar 2017 at 9:36 AM, Jonathan Haddad wrote: > +1 > On Mon, Mar 20, 2017 at 6:33 PM Jason Brown wrote: > > > +1 > > On Mon, Mar 20, 2017 at 18:21 Anthony Grasso > > wrote: > > > > > +1 > > > > > > On 21 March 2017 at 09:32, 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 > > > > > > > > > >
Re: [VOTE] Ask Infra to move github notification emails to pr@
+1 On Mon, Mar 20, 2017 at 6:33 PM Jason Brown wrote: > +1 > On Mon, Mar 20, 2017 at 18:21 Anthony Grasso > wrote: > > > +1 > > > > On 21 March 2017 at 09:32, 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 > > > > > >
Re: [VOTE] Ask Infra to move github notification emails to pr@
+1 On Mon, Mar 20, 2017 at 18:21 Anthony Grasso wrote: > +1 > > On 21 March 2017 at 09:32, 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 > > >
Re: [VOTE] Ask Infra to move github notification emails to pr@
+1 On 21 March 2017 at 09:32, 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 >
Re: [VOTE] Ask Infra to move github notification emails to pr@
+1
Re: [VOTE] Ask Infra to move github notification emails to pr@
+1 On Mon, Mar 20, 2017 at 5:32 PM, 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 >
Re: [VOTE] Ask Infra to move github notification emails to pr@
+1 On March 20, 2017 at 3:33:16 PM, Jeff Jirsa (jji...@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
[VOTE] Ask Infra to move github notification emails to pr@
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
