Re: Github action versioning

2020-08-16 Thread Gary Gregory
Hi all, As Apache Commons is a single Apache Project, we have one dev and one user ML. I think we should keep it that way, it helps Commons be Commons IMO. We also have one git commit ML. We could have an additional ML for robots which would only be used by services like github so any PR and Depen

Re: Github action versioning

2020-08-16 Thread John Patrick
I wonder if openjdk has considered all the auto generated traffic that might be triggered from github. As for JDK 16 they are moving from Mercurial to Git, and moving from internal hosting to Github. I guess we will know shortly as ramp down for JDK 16 will start something in december. Having seen

Re: Github action versioning

2020-08-16 Thread Mark Thomas
On 16/08/2020 13:58, Gary Gregory wrote: > I would not do that for Maven plugins in a POM, so I would not do that > either for GitHub actions. Fair enough. It looked to me as if these updates were being approved largely automatically hence the suggestion to skip that and just let the upgrades happ

Re: Github action versioning

2020-08-16 Thread Gary Gregory
I would not do that for Maven plugins in a POM, so I would not do that either for GitHub actions. Mailing list volume is a different topic. Gary On Sun, Aug 16, 2020, 05:55 Mark Thomas wrote: > Hi, > > I am seeing an awful lot of list traffic generated for patch updates to > github actions e.g

Re: Github action versioning

2020-08-16 Thread Rob Tompkins
> On Aug 16, 2020, at 8:29 AM, Rob Tompkins wrote: > >  > 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 wrote: >>>

Re: Github action versioning

2020-08-16 Thread Rob Tompkins
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 wrote: > >  > @Rob Tompkins > Hi. > Please consider: > 1. Most people who subscrib

Re: Github action versioning

2020-08-16 Thread Xeno Amess
@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

Re: Github action versioning

2020-08-16 Thread Rob Tompkins
> On Aug 16, 2020, at 5:59 AM, Xeno Amess 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 t

Re: Github action versioning

2020-08-16 Thread Xeno Amess
I REALLY suggest we move all dependabot mails to another mailing list. please create one. Mark Thomas 于 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 understand

Github action versioning

2020-08-16 Thread Mark Thomas
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 action