On Tue, Jul 23, 2019 at 12:31 AM Krisztián Szűcs <szucs.kriszt...@gmail.com> wrote:
> The remaining tasks are: > - Updating website (after https://github.com/apache/arrow/pull/4922 is > merged) > I'm generating the apidocs and updating the changelog. I can send the ANNOUNCEMENT once the site gets updated. > - Update JavaScript packages > Paul has published the JS packages. > - Update R packages > Anyone would like to help with it? > > On Mon, Jul 22, 2019 at 9:52 PM Krisztián Szűcs <szucs.kriszt...@gmail.com> > wrote: > >> Added a warning about that. >> >> On Mon, Jul 22, 2019 at 9:38 PM Wes McKinney <wesmck...@gmail.com> wrote: >> >>> hi folks -- we had a small snafu with the post-release tasks because >>> this patch release did not follow our normal release procedure where >>> the release candidate is usually based off of master. >>> >>> When we prepare a patch release that is based on backported commits >>> into a maintenance branch, we DO NOT need to rebase master or any PRs. >>> So we need to update the release management instructions to indicate >>> that these steps should be skipped for future patch releases (or any >>> release that isn't based on master at some point in time). >>> >>> - Wes >>> >>> On Mon, Jul 22, 2019 at 10:46 AM Krisztián Szűcs >>> <szucs.kriszt...@gmail.com> wrote: >>> > >>> > Hi, >>> > >>> > The 0.14.1 RC0 vote carries with 4 binding +1 (and 1 non-binding +1) >>> votes. >>> > Thanks for helping verify the RC! >>> > I'm moving on to the post-release tasks [1] once github resolves its >>> > partially >>> > degraded service issues [2]. Any help is appreciated. >>> > >>> > - Krisztian >>> > >>> > [1]: >>> > >>> https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-Post-releasetasks >>> > [2]: https://www.githubstatus.com/ >>> > >>> > On Mon, Jul 22, 2019 at 4:23 PM Krisztián Szűcs < >>> szucs.kriszt...@gmail.com> >>> > wrote: >>> > >>> > > +1 (binding) >>> > > >>> > > Ran both the source and binary verification scripts on macOS Mojave. >>> > > Also tested the wheels in python docker containers and on OSX. >>> > > >>> > > On Thu, Jul 18, 2019 at 11:48 PM Sutou Kouhei <k...@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.14.1 0 >>> > >> * dev/release/verify-release-candidate.sh binaries 0.14.1 0 >>> > >> >>> > >> with: >>> > >> >>> > >> * gcc (Debian 8.3.0-7) 8.3.0 >>> > >> * openjdk version "1.8.0_212" >>> > >> * ruby 2.7.0dev (2019-07-16T13:03:25Z trunk 6ab95fb741) >>> [x86_64-linux] >>> > >> * Node.JS v12.1.0 >>> > >> * go version go1.11.6 linux/amd64 >>> > >> * nvidia-cuda-dev 9.2.148-7 >>> > >> >>> > >> I re-run C# tests by the following command line sometimes: >>> > >> >>> > >> TEST_DEFAULT=0 TEST_SOURCE=1 TEST_CSHARP=1 >>> > >> dev/release/verify-release-candidate.sh source 0.14.1 0 >>> > >> >>> > >> But "sourcelink test" is always failed: >>> > >> >>> > >> + sourcelink test >>> > >> artifacts/Apache.Arrow/Release/netstandard1.3/Apache.Arrow.pdb >>> > >> The operation was canceled. >>> > >> >>> > >> I don't think that this is a broker. >>> > >> >>> > >> >>> > >> Thanks, >>> > >> -- >>> > >> kou >>> > >> >>> > >> In < >>> cahm19a5jpetwjj4uj-1zoqjzqdcejj-ky673uv83jtfcoyp...@mail.gmail.com> >>> > >> "[VOTE] Release Apache Arrow 0.14.1 - RC0" on Wed, 17 Jul 2019 >>> 04:54:33 >>> > >> +0200, >>> > >> Krisztián Szűcs <szucs.kriszt...@gmail.com> wrote: >>> > >> >>> > >> > Hi, >>> > >> > >>> > >> > I would like to propose the following release candidate (RC0) of >>> Apache >>> > >> > Arrow version 0.14.1. This is a patch release consiting of 47 >>> resolved >>> > >> > JIRA issues[1]. >>> > >> > >>> > >> > This release candidate is based on commit: >>> > >> > 5f564424c71cef12619522cdde59be5f69b31b68 [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.14.1 >>> > >> > [ ] +0 >>> > >> > [ ] -1 Do not release this as Apache Arrow 0.14.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.14.1 >>> > >> > [2]: >>> > >> > >>> > >> >>> https://github.com/apache/arrow/tree/5f564424c71cef12619522cdde59be5f69b31b68 >>> > >> > [3]: >>> > >> >>> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-0.14.1-rc0 >>> > >> > [4]: https://bintray.com/apache/arrow/centos-rc/0.14.1-rc0 >>> > >> > [5]: https://bintray.com/apache/arrow/debian-rc/0.14.1-rc0 >>> > >> > [6]: https://bintray.com/apache/arrow/python-rc/0.14.1-rc0 >>> > >> > [7]: https://bintray.com/apache/arrow/ubuntu-rc/0.14.1-rc0 >>> > >> > [8]: >>> > >> > >>> > >> >>> https://github.com/apache/arrow/blob/5f564424c71cef12619522cdde59be5f69b31b68/CHANGELOG.md >>> > >> > [9]: >>> > >> > >>> > >> >>> https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates >>> > >> >>> > > >>> >>
