Sure. That’s why you’ve pulled me from a “no” to a non-blocking dissenting opinion. I will go with community consensus at this point despite my opinion (-0) (-;
-Rob > On Aug 16, 2020, at 8:25 AM, Xeno Amess <xenoam...@gmail.com> wrote: > > > @Rob Tompkins > Hi. > Please consider: > 1. Most people who subscribe commons-dev have no right to do any operations > to dependabot prs. > We can not help merge them, nor decline them & close them. Means reading such > mails are a waste of time. > 2. Most people who subscribe commons-dev actually do not really want to read > such e-mails. > 3. Dependabot mails usually have low value. Only maintainers should have some > interest in watching them. And usually it will not break anything.(Just, > usually, in most cases). > 4. Dependabot mails are flooding. They are too many. > 5. Dependabot mails cause argues about them (this happened several times this > two weeks). > > Well my idea is we create a new mailing list named "commons-dev-auto" or > "commons-dev-bot", who contains all the auto-email. > > > I want the emails as bots should be treated as people in some sense. > > But the reality is the bot is not people. > Besides, if there be such a people who make that much pr, will you promise > review every of those prs, and do not complain about him be flooding? > > Rob Tompkins <chtom...@gmail.com> 于2020年8月16日周日 下午8:02写道： >> >> >> > On Aug 16, 2020, at 5:59 AM, Xeno Amess <xenoam...@gmail.com> wrote: >> > >> > I REALLY suggest we move all dependabot mails to another mailing list. >> > please create one. >> >> Your point has pulled me from a -1 to a -0, where I want the emails as bots >> should be treated as people in some sense. That said, I’m curious as to what >> others think... >> >> Thoughts? >> >> -Rob >> >> > >> > Mark Thomas <ma...@apache.org> 于 2020年8月16日周日 下午5:55写道： >> > >> >> Hi, >> >> >> >> I am seeing an awful lot of list traffic generated for patch updates to >> >> github actions e.g. updating from v1.4.0 to v1.4.1 >> >> >> >> Having read [1], my understanding is that we can specify v1 and that >> >> will always point to the latest 1.x.x release. >> >> >> >> Would it not be better to specify v1 for these actions as that way: >> >> - we use the latest version automatically (until 2.x.x is released) >> >> - we avoid all the noise on the mailing list >> >> >> >> Mark >> >> >> >> >> >> >> >> [1] https://docs.github.com/en/actions/creating-actions/about-actions >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >>
