If anyone has any feature requests for http://apache.jamesthom.as please open issues @ https://github.com/jthomas/openwhisk-release-verification/issues
PRs always welcome ;) It is just three (simple) Node.js openwhisk actions powering the backend to do the verification. On Mon, 25 Mar 2019 at 15:05, Chetan Mehrotra <[email protected]> wrote: > Thanks Rodric and James for such tooling. This would greatly reduce the > friction in voting for releases. > > In Apache Sling we have evolved the voting process over the time [1] which > has helped in getting people to vote. > > Chetan Mehrotra > [1] > > https://sling.apache.org/documentation/development/release-management.html#starting-the-vote > > > On Mon, Mar 25, 2019 at 8:19 PM Rodric Rabbah <[email protected]> wrote: > > > This email is in response to Chetan raising the following "May be we > > automate some of the steps using a shell script similar to > > > > > https://github.com/apache/sling-tooling-release/blob/master/check_staged_release.sh > > " > > in one of the recent release vote threads. > > > > Thanks to James Thomas, we have a web-based verification tool that > > automates the release candidate checks so it's much easier now to verify > > and vote on the releases. Source available at > > https://github.com/jthomas/openwhisk-release-verification and you can > try > > it out here http://apache.jamesthom.as/ per comment on Slack earlier > > today. > > > > And I opened a PR to add my bash scripts which I called `rcverify` here > > https://github.com/apache/incubator-openwhisk-release/pull/254. This was > > previously a gist which I'll delete if the PR is accepted (see [1] for > > reference). > > > > [1] rcverify gist > > https://gist.github.com/rabbah/0f9e138c9088758c30fe31f05b893041 > > > > -r > > > -- Regards, James Thomas
