arrow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Neal Richardson <neal.p.richard...@gmail.com>
Subject Re: [VOTE] Release Apache Arrow 0.15.1 - RC0
Date Sun, 03 Nov 2019 14:51:52 GMT
Yes, I’m on it. 

Neal

> On Nov 3, 2019, at 4:38 AM, Krisztián Szűcs <szucs.krisztian@gmail.com> wrote:
> 
> Thanks Wes!
> 
> The cpp, python and R conda packages are updated, so the only remaining
> task is to update the R packages. @Neal could you please help with that?
> 
> - [x] marking the released version as "RELEASED" on JIRA
> - [x] uploading source release artifacts to SVN
> - [x] uploading binary release artifacts to Bintray
> - [x] updating the Arrow website
> - [x] updating website with new API documentation
> - [x] announcing release
> - [x] python wheels
> - [x] python source distribution
> - [x] conda packages
> - [x] homebrew packages
> - [x] java maven artifacts
> - [x] ruby gems
> - [x] javascript npm packages
> - [x] .NET nuget packages
> - [ ] R packages
> 
>> On Sat, Nov 2, 2019 at 10:33 PM Wes McKinney <wesmckinn@gmail.com> wrote:
>> 
>> OK, Sphinx docs are updated, I submitted a patch ARROW-7054 so we can
>> work around this again in the future if needed.
>> 
>>> On Sat, Nov 2, 2019 at 3:48 PM Wes McKinney <wesmckinn@gmail.com> wrote:
>>> 
>>> I built the docs but ran into a bug
>>> 
>>> https://issues.apache.org/jira/browse/ARROW-7053
>>> 
>>> We may need to spoof the version for Sphinx's benefit (there was a
>>> patch about this recently also), but it would be good to fix the
>>> underlying problem
>>> 
>>> On Fri, Nov 1, 2019 at 4:34 PM Krisztián Szűcs
>>> <szucs.krisztian@gmail.com> wrote:
>>>> 
>>>> Status of the post release tasks:
>>>> 
>>>> - [x] marking the released version as "RELEASED" on JIRA
>>>> - [x] uploading source release artifacts to SVN
>>>> - [x] uploading binary release artifacts to Bintray
>>>> - [x] updating the Arrow website
>>>> - [ ] updating website with new API documentation
>>>> - [x] announcing release
>>>> - [x] python wheels
>>>> - [x] python source distribution
>>>> - [ ] conda packages
>>>> - [x] homebrew packages
>>>> - [x] java maven artifacts
>>>> - [x] ruby gems
>>>> - [x] javascript npm packages
>>>> - [x] .NET nuget packages
>>>> 
>>>> I had trouble with re-staging the maven artifacts. The re-staging
>>>> got a bit more complicated because of the Gandiva and ORC
>>>> JNI, so I've used the following commands:
>>>> 
>>>> # build the jni bindings similarly like the 01-perform.sh does
>>>> mkdir -p cpp/java-build
>>>> pushd cpp/java-build
>>>> cmake \
>>>>  -DARROW_GANDIVA=ON \
>>>>  -DARROW_GANDIVA_JAVA=ON \
>>>>  -DARROW_JNI=ON \
>>>>  -DARROW_ORC=ON \
>>>>  -DCMAKE_BUILD_TYPE=release \
>>>>  -G Ninja \
>>>>  ..
>>>> ninja
>>>> popd
>>>> # go in the java subfolder
>>>> pushd java
>>>> # stage the artifacts using both the apache-release and arrow-jni profiles
>>>> mvn -Papache-release,arrow-jni -Darrow.cpp.build.dir=$(realpath
>>>> ../cpp/java-build) deploy
>>>> popd
>>>> 
>>>> The staging, verification then the release went fine and the 0.15.1
>>>> release is available under the apache repository repository.apache.org
>>>> My issue that seemingly the version doesn't propagate to the maven
>>>> central.
>>>> Could someone more experienced with maven verify that the release
>>>> is available as expected?
>>>> 
>>>> Thanks, Krisztian
>>>> 
>>>> On Fri, Nov 1, 2019 at 9:23 PM Krisztián Szűcs
>>>> <szucs.krisztian@gmail.com> wrote:
>>>>> 
>>>>> Status of the post release tasks:
>>>>> 
>>>>> - [x] marking the released version as "RELEASED" on JIRA
>>>>> - [x] uploading source release artifacts to SVN
>>>>> - [x] uploading binary release artifacts to Bintray
>>>>> - [ ] updating the Arrow website
>>>>> - [ ] updating website with new API documentation
>>>>> - [ ] announcing release
>>>>> - [x] python wheels
>>>>> - [x] python source distribution
>>>>> - [ ] conda packages
>>>>> - [x] homebrew packages
>>>>> - [ ] java maven artifacts (the staged artefacts is missing, so I need
>>>>> to re-stage)
>>>>> - [x] ruby gems
>>>>> - [x] javascript npm packages
>>>>> - [x] .NET nuget packages
>>>>> - [x] rust packages (should fix ARROW-6801 for the next release)
>>>>> - [ ] R packages
>>>>> 
>>>>>> On Fri, Nov 1, 2019 at 5:21 PM Wes McKinney <wesmckinn@gmail.com>
wrote:
>>>>>> 
>>>>>> I'll update the Sphinx documentation
>>>>>> 
>>>>>> On Fri, Nov 1, 2019 at 10:41 AM Krisztián Szűcs
>>>>>> <szucs.krisztian@gmail.com> wrote:
>>>>>>> 
>>>>>>> Post release tasks:
>>>>>>> 
>>>>>>> - [x] marking the released version as "RELEASED" on JIRA
>>>>>>> - [x] uploading source release artifacts to SVN
>>>>>>> - [-] uploading binary release artifacts to Bintray (in-progress)
>>>>>>> - [ ] updating the Arrow website
>>>>>>> - [ ] updating website with new API documentation
>>>>>>> - [ ] announcing release
>>>>>>> - [x] python wheels
>>>>>>> - [x] python source distribution
>>>>>>> - [ ] conda packages
>>>>>>> - [x] homebrew packages
>>>>>>> - [ ] java maven artifacts (the staged artefacts is missing,
so I need
>>>>>>> to re-stage)
>>>>>>> - [ ] ruby gems
>>>>>>> - [x] javascript npm packages
>>>>>>> - [ ] .NET nuget packages
>>>>>>> - [x] rust packages (should fix ARROW-6801 for the next release)
>>>>>>> - [ ] R packages
>>>>>>> 
>>>>>>> On Fri, Nov 1, 2019 at 3:36 PM Krisztián Szűcs
>>>>>>> <szucs.krisztian@gmail.com> wrote:
>>>>>>>> 
>>>>>>>> The vote carries with 4 binding +1 votes and 2 non-binding
+1 votes.
>>>>>>>> 
>>>>>>>> I'm starting the post-release tasks, if anyone wants to help
please let me know.
>>>>>>>> 
>>>>>>>> On Fri, Nov 1, 2019 at 3:32 PM Krisztián Szűcs
>>>>>>>> <szucs.krisztian@gmail.com> wrote:
>>>>>>>>> 
>>>>>>>>> +1 (binding)
>>>>>>>>> 
>>>>>>>>> - verified source on macOS Mojave
>>>>>>>>> - verified binaries
>>>>>>>>> - verified wheels on Linux, macOS
>>>>>>>>> 
>>>>>>>>>> On Wed, Oct 30, 2019 at 7:41 PM Wes McKinney <wesmckinn@gmail.com>
wrote:
>>>>>>>>>> 
>>>>>>>>>> +1 (binding)
>>>>>>>>>> 
>>>>>>>>>> * Verified source on Ubuntu 18.04 (using 0.15.1 RC
verification script)
>>>>>>>>>> * Verified wheels on Linux, macOS, and Windows using
>>>>>>>>>> "verify-release-candidate.sh wheels ..." and
>>>>>>>>>> verify-release-candidate-wheels.bat
>>>>>>>>>> * Verified Linux binaries
>>>>>>>>>> 
>>>>>>>>>> Thanks for fixing the macOS wheel!
>>>>>>>>>> 
>>>>>>>>>> On Wed, Oct 30, 2019 at 11:24 AM Krisztián Szűcs
>>>>>>>>>> <szucs.krisztian@gmail.com> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> Hi,
>>>>>>>>>>> 
>>>>>>>>>>> I've uploaded the correct wheel for CPython 3.7
on macOS, also
>>>>>>>>>>> tested it locally, it works properly. Created
a JIRA [1] to test the
>>>>>>>>>>> wheels in the release verification script similarly
like we test the
>>>>>>>>>>> linux packages, this should catch both the uploading
issues and
>>>>>>>>>>> the linking errors causing most of the troubles
with wheels.
>>>>>>>>>>> 
>>>>>>>>>>> Thanks, Krisztian
>>>>>>>>>>> 
>>>>>>>>>>> [1]: https://issues.apache.org/jira/browse/ARROW-7032
>>>>>>>>>>> 
>>>>>>>>>>> On Tue, Oct 29, 2019 at 6:40 PM Krisztián Szűcs
>>>>>>>>>>> <szucs.krisztian@gmail.com> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> I have locally the same binary, so something
must have happened
>>>>>>>>>>>> silently during the downloading process,
without exiting with an error.
>>>>>>>>>>>> The proper wheel is available under the GitHub
release for that
>>>>>>>>>>>> particular crossbow task here [1].
>>>>>>>>>>>> I'll download, sign and upload it to Bintray
tomorrow evening (CET).
>>>>>>>>>>>> 
>>>>>>>>>>>> [1]: https://github.com/ursa-labs/crossbow/releases/tag/build-722-travis-wheel-osx-cp37m
>>>>>>>>>>>> 
>>>>>>>>>>>>> On Mon, Oct 28, 2019 at 11:00 PM Wes
McKinney <wesmckinn@gmail.com> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I started looking at some of the Python
wheels and found that the
>>>>>>>>>>>>> macOS Python 3.7 wheel is corrupted.
Note that it's only 101KB while
>>>>>>>>>>>>> the other macOS wheels are ~35MB.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Eyeballing the file list at
>>>>>>>>>>>>> 
>>>>>>>>>>>>> https://bintray.com/apache/arrow/python-rc/0.15.1-rc0#files/python-rc/0.15.1-rc0
>>>>>>>>>>>>> 
>>>>>>>>>>>>> it seems this is the only wheel with
this issue, but this suggests
>>>>>>>>>>>>> that we should prioritize some kind of
wheel integrity check using
>>>>>>>>>>>>> Crossbow jobs. An issue for this is
>>>>>>>>>>>>> 
>>>>>>>>>>>>> https://issues.apache.org/jira/browse/ARROW-2880
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I'm going to check out some other wheels
to see if they are OK, but
>>>>>>>>>>>>> maybe just this one wheel can be regenerated?
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Sun, Oct 27, 2019 at 4:31 PM Sutou
Kouhei <kou@clear-code.com> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> +1 (binding)
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I ran the followings on Debian GNU/Linux
sid:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>  * TEST_CSHARP=0 \
>>>>>>>>>>>>>>      JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
\
>>>>>>>>>>>>>>      CUDA_TOOLKIT_ROOT=/usr \
>>>>>>>>>>>>>>        dev/release/verify-release-candidate.sh
source 0.15.1 0
>>>>>>>>>>>>>>  * dev/release/verify-release-candidate.sh
binaries 0.15.1 0
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> with:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>  * gcc (Debian 9.2.1-8) 9.2.1 20190909
>>>>>>>>>>>>>>  * openjdk version "1.8.0_232-ea"
>>>>>>>>>>>>>>  * Node.JS v12.1.0
>>>>>>>>>>>>>>  * go version go1.12.10 linux/amd64
>>>>>>>>>>>>>>  * nvidia-cuda-dev 10.1.105-3+b1
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Notes:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>  * C# sourcelink is failed as usual.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>  * We can't use dev/release/verify-release-candidate.sh
on
>>>>>>>>>>>>>>    master to verify source because
it depends on the latest
>>>>>>>>>>>>>>    archery. We need to use
>>>>>>>>>>>>>>    dev/release/verify-release-candidate.sh
in 0.15.1.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> kou
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> In <CAHM19a55Ex1aRWoq7mpZHkedeMRCHXm2dgS=FDm_8Cqw6Q_dKQ@mail.gmail.com>
>>>>>>>>>>>>>>  "[VOTE] Release Apache Arrow 0.15.1
- RC0" on Fri, 25 Oct 2019 20:43:07 +0200,
>>>>>>>>>>>>>>  Krisztián Szűcs <szucs.krisztian@gmail.com>
wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> I would like to propose the following
release candidate (RC0) of Apache
>>>>>>>>>>>>>>> Arrow version 0.15.1. This is
a patch release consisting of 36 resolved
>>>>>>>>>>>>>>> JIRA issues[1].
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> This release candidate is based
on commit:
>>>>>>>>>>>>>>> b789226ccb2124285792107c758bb3b40b3d082a
[2]
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> The source release rc0 is hosted
at [3].
>>>>>>>>>>>>>>> The binary artifacts are hosted
at [4][5][6][7].
>>>>>>>>>>>>>>> The changelog is located at [8].
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Please download, verify checksums
and signatures, run the unit tests,
>>>>>>>>>>>>>>> and vote on the release. See
[9] for how to validate a release candidate.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> The vote will be open for at
least 72 hours.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> [ ] +1 Release this as Apache
Arrow 0.15.1
>>>>>>>>>>>>>>> [ ] +0
>>>>>>>>>>>>>>> [ ] -1 Do not release this as
Apache Arrow 0.15.1 because...
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> [1]: https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%200.15.1
>>>>>>>>>>>>>>> [2]: https://github.com/apache/arrow/tree/b789226ccb2124285792107c758bb3b40b3d082a
>>>>>>>>>>>>>>> [3]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-0.15.1-rc0
>>>>>>>>>>>>>>> [4]: https://bintray.com/apache/arrow/centos-rc/0.15.1-rc0
>>>>>>>>>>>>>>> [5]: https://bintray.com/apache/arrow/debian-rc/0.15.1-rc0
>>>>>>>>>>>>>>> [6]: https://bintray.com/apache/arrow/python-rc/0.15.1-rc0
>>>>>>>>>>>>>>> [7]: https://bintray.com/apache/arrow/ubuntu-rc/0.15.1-rc0
>>>>>>>>>>>>>>> [8]: https://github.com/apache/arrow/blob/b789226ccb2124285792107c758bb3b40b3d082a/CHANGELOG.md
>>>>>>>>>>>>>>> [9]: https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates

Mime
View raw message