I believe the shell script tooling can be used for quickly validating the release for votes.
We can enhance the web tooling to simplify process for preparing the release which still has some manual aspects. 1. Generate a email from a template with required links 2. Compute the list of commits/issue (or better have a git release link) which describes what all is new from last release. Current release vote mail only lists the sha and legal stuff which is of not much use to end user. So having links to set of issues/PR included in the release would be useful Chetan Mehrotra On Mon, Mar 25, 2019 at 11:10 PM Carlos Santana <[email protected]> wrote: > Using the website I would think it doesn’t count as verifying the > artifacts. > > Just playing devils advocate here. > > Going to a website and selecting something from a Dropbox and see green > checks don’t know if the useful for the person doing the voting. Maybe > taking the code from the website or bash scripts and running locally seems > more real. > > - Carlos Santana > @csantanapr > > > On Mar 25, 2019, at 12:18 PM, James Thomas <[email protected]> wrote: > > > > 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 >
