Transferring to openzipkin-contrib seems reasonable to me so others can more easily make changes.
On Fri, Feb 15, 2019, 00:58 Brian Devins-Suresh <[email protected]> wrote: > Hi Zoltan, to be honest I ended up doing the checks by hand on my work > computer so will have to recreate them. > I do however have a repo with the start of my dockerfile [1]. I added a > note about the approach I had planned on > taking in a comment. Please feel free to send me a PR, I could even > transfer to openzipkin-contrib if others were > Ok with it. > > - Brian > > 1: https://github.com/devinsba/apache-release-verification > > On Thu, Feb 14, 2019 at 5:21 AM Zoltán Nagy <[email protected]> wrote: > > > Brian, do you want to share that script? I'm developing an itch to write > it > > myself, and while I hate duplicate effort, who knows what I might end up > > doing :p > > > > On Thu, Feb 14, 2019, 06:26 Mick Semb Wever <[email protected] wrote: > > > > > > > > > For example, there's another plugin "rat" > > > > which checks library dependencies. Presence of that plugin means we > > > > don't need to re-validate the dependency tree by hand. I think > > > > transitively, we can use this logic to remove a manual step of > > > > verifying license headers. wdyt? > > > > > > > > > Yes! The use of the "rat" plugin is thoroughly recommended. > > > > > > A script/plugin that does any further validation of a release would be > > > hugely appreciated by other Apache projects! > > > (There's a lot of manual validation of releases that kinda crazy that > > > we're still doing) > > > > > > regards, > > > Mick > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > >
