Rust implementation can be compiled to WebAssembly and is released
biweekly. The Javascript version compiled from Rust may not satisfy all
Javascript users, but maybe there could be some collaboration to reduce
duplicated efforts?
On 11/23/21 9:52 PM, Dominik Moritz wrote:
Ahh, thank you for the clarification. There are no breaking changes in
this point release, just fixes.
@PMC, could you please vote on this point release.
Would anyone volunteer as the release manager with me to give me a better
understanding of the process?
On Nov 23, 2021 at 13:09:47, Benson Muite <[email protected]>
wrote:
https://issues.apache.org/jira/browse/ARROW-14801
Rust has its own repository and does frequent point releases:
https://github.com/apache/arrow-rs/tree/master/dev/release
however, even point releases require 3 PMC binding +1 votes and API
breaking changes can only take place on major releases.
Many of the tests for releases can be automated, possibly relieving some
of the PMC burden in the current process. Judgement on code quality and
software license is still required though[1]. Similarly, releases need
to be signed.
[1] https://infra.apache.org/release-publishing.html
On 11/23/21 7:33 PM, Dominik Moritz wrote:
I tested Node v14.18.1 and tests pass. I think we can go ahead and make a
release.
@Benson, could you help me update the script to work off of branches. I
don’t know what the expected process for release verification is. I’d be
happy to adopt another process.
On Nov 20, 2021 at 09:57:53, Dominik Moritz <[email protected]> wrote:
Thanks for catching that.
Jest is used for running the tests and jest supports node 14.15. Could we
switch to node 14.15 instead of 14.0 for this test?
On Nov 20, 2021 at 05:37:00, Benson Muite <[email protected]>
wrote:
Hi,
Tested this on AlmaLinux 8. Following steps:
export NVM_DIR="`pwd`/.nvm"
mkdir -p $NVM_DIR
curl -o-
https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | \
PROFILE=/dev/null bash
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
nvm install --lts
npm install -g yarn
git clone https://github.com/apache/arrow
cd arrow
git checkout release-6.0.2-js
cd js
yarn --frozen-lockfile
yarn run-s clean:all lint build
yarn test
Tests pass.
yarn 1.22.17
npm 8.1.0
node 16.13.0
Tests also pass on
node 17.0.0
Node 14 is supported until 2023, however if one tries to use Node 14,
one gets the error:
[email protected]: The engine "node" is incompatible with this module.
Expected version "^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0". Got
"14.0.0"
error Found incompatible module.
The current release verification script could be update to support
testing directly from a branch if this will be the point release process
in future.
On 11/20/21 12:25 AM, Dominik Moritz wrote:
Hi,
I would like to propose a patch release for Arrow JS. The release is
forked
off of maint-6.0.x and available at
https://github.com/apache/arrow/tree/release-6.0.2-js.
The release contains two fixes for the js bundle:
ARROW-14773: [JS] Fix sourcemap paths
<https://github.com/apache/arrow/pull/11741>
ARROW-14774: [JS] Correct package exports
<https://github.com/apache/arrow/pull/11742>
[ ] +1 Release this as Apache Arrow JS 6.0.2
[ ] +0
[ ] -1 Do not release this as Apache Arrow JS 6.0.2 because...
Thank you,
Dominik
