With 4 +1 (3 binding), this VOTE passes. I will upload the release and send out 
the announcement later.

@Paul, Brian can one of you write a short blog post about the new things in 0.4 
for the Arrow blog?

Uwe

On Mon, Feb 4, 2019, at 10:45 PM, Paul Taylor wrote:
> +1
> 
> verified on 18.04.1-Ubuntu and node v11.6.0
> 
> > On 1/31/19 9:38 AM, Krisztián Szűcs wrote:
> > +1 (binding),
> > 
> > verified on OSX Mojave and Node v11.4.0
> > 
> >> On Thu, Jan 31, 2019 at 6:06 PM Brian Hulette <hulet...@gmail.com> wrote:
> >> 
> >> +1
> >> 
> >> verified on Archlinux with Node v11.9.0
> >> 
> >> Thanks a lot for putting the RC together Uwe!
> >> 
> >>> On Thu, Jan 31, 2019 at 8:08 AM Uwe L. Korn <m...@uwekorn.com> wrote:
> >>> 
> >>> +1 (binding),
> >>> 
> >>> verified on Ubuntu 16.04 with
> >>> `./dev/release/js-verify-release-candidate.sh 0.4.0 1` and Node v11.9.0
> >> via
> >>> nvm.
> >>> 
> >>> Uwe
> >>> 
> >>>> On Thu, Jan 31, 2019, at 5:07 PM, Uwe L. Korn wrote:
> >>>> Hello all,
> >>>> 
> >>>> I would like to propose the following release candidate (rc1) of Apache
> >>>> Arrow JavaScript version 0.4.0.
> >>>> 
> >>>> The source release rc1 is hosted at [1].
> >>>> 
> >>>> This release candidate is based on commit
> >>>> 6009eaa49ae29826764eb6e626bf0d12b83f3481
> >>>> 
> >>>> Please download, verify checksums and signatures, run the unit tests,
> >>> and vote
> >>>> on the release. The easiest way is to use the JavaScript-specific
> >> release
> >>>> verification script dev/release/js-verify-release-candidate.sh.
> >>>> 
> >>>> The vote will be open for at least 72 hours.
> >>>> 
> >>>> [ ] +1 Release this as Apache Arrow JavaScript 0.4.0
> >>>> [ ] +0
> >>>> [ ] -1 Do not release this as Apache Arrow JavaScript 0.4.0 because...
> >>>> 
> >>>> 
> >>>> How to validate a release signature:
> >>>> https://httpd.apache.org/dev/verification.html
> >>>> 
> >>>> [1]:
> >> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-js-0.4.0-rc1/
> >>>> [2]:
> >> https://github.com/apache/arrow/tree/6009eaa49ae29826764eb6e626bf0d12b83f3481
> 

Reply via email to