+1. There have been a few times I've attempted to run the verification
scripts. They have failed, but I was pretty confident it was a problem
with my environment mixing with the verification script and not a problem
in the software itself and I didn't take the time to debug the verification
scrip
I concur, a minimally scoped verification script for the actual voting
process without any binary verification etc. should be created. The ease in
verifying a release will lower the burden to participate in the vote which
is good for the community and will even be necessary if we ever want to
incre
I would second this notion that manually running tests that are already
covered as part of CI as part of the release process is of (very) limited
value.
While we do the same thing (compile and run some tests) as part of the Rust
release this has never caught any serious defect I am aware of and we
Well, if the main objective is to just follow the ASF Release
guidelines, then our verification process can be simplified drastically.
The ASF indeed just requires:
"""
Every ASF release MUST contain one or more source packages, which MUST
be sufficient for a user to build and test the relea
I agree that this is a great time to look at improving the verification
process. One solution I've seen work fairly well is to convert large bash
scripts into a lightweight ETL pipeline that caches the results/status of
each node as it executes. That way, restarting a pipeline at the right
checkpoi
Hi,
One of the challenges we have when doing a release is verification and voting.
Currently the Arrow verification process is quite long, tedious and error prone.
I would like to use this email to get feedback and user requests in
order to improve the process.
Several things already on my mind
it will be clear
> to everyone that the standards have been met when we run the tests.
>
I understand where you're coming from, but the release verification
process is intended to collect idiosyncratic information from people
attempting to use the software in different ways. I doubt that
Hi all,
[Splitting off from the [VOTE] discussion thread]
I wonder if there are things we can do to make for a smoother release next
time. This was the first release I participated in with the Arrow project,
and there were some aspects that were surprising to me. It seemed odd that
"release verifi
