You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@arrow.apache.org by Wes McKinney <we...@gmail.com> on 2019/06/21 19:58:54 UTC

[DISCUSS] Making the Arrow 0.14 release, outstanding items

hi folks,

It seems like we are on the home stretch for the 0.14 release as we
have been working intensely to stabilize builds and packaging jobs
this week and last

See status page at

https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release

I note that there are 64 open issues still, not all of which are
absolutely necessary to be able to release. If you are a stakeholder
in any component of the project, can you please:

* Remove any issue from the 0.14.0 fix version that you are certain
will not be resolved in the next week or less
* Set to Blocker any issue that you believe must be fixed before releasing
* Adding any Blocker issues to the 0.14 Fix Version if not there already

In theory we could cut a release candidate sometime next week, or in
the worst case scenario the week of July 1.

If there's anything else that you'd like to discuss on this please
chime in here.

Thanks
Wes

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Sutou Kouhei <ko...@clear-code.com>.

Hi,

Binary artifacts are built. I'm uploading them to Bintray
but I reach Bintray's API limit...

https://bintray.com/docs/api/#_limits says

> Limits only apply to resources that do not belong to a
> user or to the organization the user is part of.

So I request to join https://bintray.com/apache organization
to avoid API limit.

I'm waiting for response from https://bintray.com/apache
organization.


Thanks,
--
kou

In <20...@clear-code.com>
  "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Sat, 29 Jun 2019 07:56:37 +0900 (JST),
  Sutou Kouhei <ko...@clear-code.com> wrote:

> Hi,
> 
> ursabot doesn't support --arrow-version crossbow.py option.
> So I used ursa-labs/crossbow from command line.
> 
> Crossbow build: https://github.com/ursa-labs/crossbow/branches/all?utf8=%E2%9C%93&query=build-660
> 
> I'll send a release vote e-mail when these builds are
> completed and uploads built binaries.
> 
> Apache Arrow 0.14.0 RC0 source is already uploaded to
> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-0.14.0-rc0 .
> 
> So we can run at least
> "dev/release/verify-release-candidate.sh source 0.14.0 0"
> before I send a release vote e-mail.
> 
> 
> Thanks,
> --
> kou
> 
> In <CA...@mail.gmail.com>
>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, 28 Jun 2019 16:22:34 -0500,
>   Wes McKinney <we...@gmail.com> wrote:
> 
>> hi Kou,
>> 
>> You can already push to https://github.com/ursa-labs/crossbow so I
>> think if you use that as your Crossbow queue then you can benefit from
>> having the CI systems pre-configured
>> 
>> On Fri, Jun 28, 2019 at 4:20 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>>>
>>> Hi Krisztián,
>>>
>>> OK. I'll use ursabot!
>>>
>>>
>>> Thanks,
>>> --
>>> kou
>>>
>>> In <CA...@mail.gmail.com>
>>>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, 28 Jun 2019 15:02:32 +0200,
>>>   Krisztián Szűcs <sz...@gmail.com> wrote:
>>>
>>> > @Kou I suggest You to use ursa-labs/crossbow repository for building the
>>> > binaries, because the packaging builds are using azure pipelines, travis
>>> > and appveyor now. You may setup azure pipelines for your crossbow
>>> > instance as well, but it is possibly easier to use ursa-labs' one.
>>> > Also You can use the comment mechanism, e.g. opening a PR for the
>>> > release branch and using `@ursabot crossbow package -g wheel -g conda -g
>>> > linux`.
>>> > For dowloading the artifacts You'll still need to clone ursa-labs/crossbow
>>> > though.
>>> >
>>> > On Fri, Jun 28, 2019 at 8:29 AM Sutou Kouhei <ko...@clear-code.com> wrote:
>>> >
>>> >> Go ahead when a committer says LGTM!
>>> >>
>>> >> In <CA...@mail.gmail.com>
>>> >>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Thu,
>>> >> 27 Jun 2019 22:50:35 -0700,
>>> >>   Neal Richardson <ne...@gmail.com> wrote:
>>> >>
>>> >> > I'd like to squeeze https://issues.apache.org/jira/browse/ARROW-5773
>>> >> into
>>> >> > 0.14 if you'll allow. It's just documentation. I just put the PR up now:
>>> >> > https://github.com/apache/arrow/pull/4736
>>> >> >
>>> >> > Thanks,
>>> >> > Neal
>>> >> >
>>> >> > On Thu, Jun 27, 2019 at 9:55 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>>> >> >
>>> >> >> We can merge pull request that doesn't change pom.xml for
>>> >> >> 0.14.0 until I finished ARROW-4301 and ARROW-5695.
>>> >> >>
>>> >> >> In <20...@clear-code.com>
>>> >> >>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
>>> >> Fri,
>>> >> >> 28 Jun 2019 13:40:59 +0900 (JST),
>>> >> >>   Sutou Kouhei <ko...@clear-code.com> wrote:
>>> >> >>
>>> >> >> > Thanks!
>>> >> >> >
>>> >> >> > I'm testing ARROW-4301 (00-prepare.sh) and ARROW-5695
>>> >> >> > (verify-release-candidate.sh).
>>> >> >> >
>>> >> >> > ARROW-4301: We need to build C++ with Gandiva and ORC in
>>> >> >> > 00-prepare.sh. I'm working on this.
>>> >> >> >
>>> >> >> > ARROW-5695: I'll merge this when I confirmed all
>>> >> >> > verification patterns are passed with master. I'm running.
>>> >> >> >
>>> >> >> > I'll create RC0 when I finished them.
>>> >> >> >
>>> >> >> > For ARROW-5579, please merge it after 0.14.0. I don't want
>>> >> >> > to add more pom.xml changes for now.
>>> >> >> >
>>> >> >> >
>>> >> >> > Thanks,
>>> >> >> > --
>>> >> >> > kou
>>> >> >> >
>>> >> >> > In <
>>> >> CAJPUwMB_he9up4BcvaKTvxaBLuu2uNQwxvn0UWq_VF9aR0H22w@mail.gmail.com>
>>> >> >> >   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
>>> >> >> Thu, 27 Jun 2019 22:35:45 -0500,
>>> >> >> >   Wes McKinney <we...@gmail.com> wrote:
>>> >> >> >
>>> >> >> >> It looks like we're down to 4 open issues. The remaining items can be
>>> >> >> >> merged at Kou's discretion. The one uncertain item is ARROW-5579 --
>>> >> >> >> shading Flatbuffers. It seems like it might not be prudent to rush in
>>> >> >> >> a patch that might potentially cause problems
>>> >> >> >>
>>> >> >> >> On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney <we...@gmail.com>
>>> >> >> wrote:
>>> >> >> >>>
>>> >> >> >>> hi folks,
>>> >> >> >>>
>>> >> >> >>> There are still 10 issues in the 0.14.0 milestone:
>>> >> >> >>>
>>> >> >> >>> * ARROW-4301: [Java] Patch up, pending review / merge
>>> >> >> >>> * ARROW-2104: [C++] Ready to merge pending CI
>>> >> >> >>> * ARROW-5500: [R] Ready to merge pending review
>>> >> >> >>> * ARROW-5718: [R] Pending review -- may not be necessary for release
>>> >> >> >>> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it
>>> >> >> >>> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is
>>> >> >> >>> working on this in PR now
>>> >> >> >>> * ARROW-5695: Patch in review / pending merge
>>> >> >> >>> * ARROW-5579: Shading Java Flatbuffers: Pending review
>>> >> >> >>> * ARROW-5138: I am looking at this now-ish to determine if a fix is
>>> >> in
>>> >> >> >>> scope for the release
>>> >> >> >>> * ARROW-5497: Publishing R / JS / Java docs -- not essential before
>>> >> >> >>> release candidate can be cut
>>> >> >> >>>
>>> >> >> >>> Is there anything else?
>>> >> >> >>>
>>> >> >> >>> Based on these outstanding patches I would guess it's going to be
>>> >> >> >>> another 12-24 hours from now before an RC can be cut
>>> >> >> >>>
>>> >> >> >>> I will also spend some time working on the blog post today
>>> >> >> >>>
>>> >> >> >>> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson
>>> >> >> >>> <ne...@gmail.com> wrote:
>>> >> >> >>> >
>>> >> >> >>> > I've got one of the blockers,
>>> >> >> >>> > https://issues.apache.org/jira/browse/ARROW-5497, about the
>>> >> >> non-sphinx
>>> >> >> >>> > language doc building. I'll spend some time on it this week. It
>>> >> >> should get
>>> >> >> >>> > done before we're wrapped up with 0.14, but if I get held up, it
>>> >> >> doesn't
>>> >> >> >>> > need to block making RC0.
>>> >> >> >>> >
>>> >> >> >>> > In other news, in order to facilitate one of the post-release
>>> >> tasks,
>>> >> >> I've
>>> >> >> >>> > started a google doc for the release announcement blog post:
>>> >> >> >>> >
>>> >> >>
>>> >> https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj
>>> >> >> >>> > . While we could wait to deal with the release announcement until
>>> >> >> after the
>>> >> >> >>> > release happens, doing it early can be a good exercise: it can
>>> >> reveal
>>> >> >> >>> > details and polishing that are important to realizing the value of
>>> >> >> the
>>> >> >> >>> > features in the release. Plus, it shouldn't take long and we can
>>> >> >> just get
>>> >> >> >>> > it out of the way.
>>> >> >> >>> >
>>> >> >> >>> > For anyone who is a maintainer/stakeholder of one of the
>>> >> languages or
>>> >> >> >>> > components of the project, please fill in the "notes" section for
>>> >> >> your
>>> >> >> >>> > component. Others could try to infer what's in the release based
>>> >> on
>>> >> >> the
>>> >> >> >>> > commit messages, but sometimes it's hard to tell what the sum of
>>> >> the
>>> >> >> parts
>>> >> >> >>> > is from that.
>>> >> >> >>> >
>>> >> >> >>> > Thanks,
>>> >> >> >>> > Neal
>>> >> >> >>> >
>>> >> >> >>> >
>>> >> >> >>> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney <wesmckinn@gmail.com
>>> >> >
>>> >> >> wrote:
>>> >> >> >>> >
>>> >> >> >>> > > hi Kou,
>>> >> >> >>> > >
>>> >> >> >>> > > Thank you for volunteering to be the release manager. I think
>>> >> many
>>> >> >> of
>>> >> >> >>> > > the issues marked as Blocker on
>>> >> >> >>> > >
>>> >> >> >>> > >
>>> >> >> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
>>> >> >> >>> > >
>>> >> >> >>> > > are being actively worked on. I'll follow up with individuals
>>> >> >> directly
>>> >> >> >>> > > and try to help get patches merged so we can be ready to release
>>> >> >> >>> > > ideally before Friday in Japan (end of workday Thursday in the
>>> >> >> USA).
>>> >> >> >>> > > In certain cases (e.g. ARROW-5335) we may have to accept a
>>> >> >> suboptimal
>>> >> >> >>> > > solution and do more work for the next release.
>>> >> >> >>> > >
>>> >> >> >>> > > Thanks
>>> >> >> >>> > > Wes
>>> >> >> >>> > >
>>> >> >> >>> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <
>>> >> kou@clear-code.com>
>>> >> >> wrote:
>>> >> >> >>> > > >
>>> >> >> >>> > > > Hi,
>>> >> >> >>> > > >
>>> >> >> >>> > > > Nobody says "I want to be a release manager". So I'll be the
>>> >> >> >>> > > > release manager for 0.14.0.
>>> >> >> >>> > > >
>>> >> >> >>> > > > I'm working on and assisting some release related issues:
>>> >> >> >>> > > >
>>> >> >> >>> > > >   * ARROW-5054 [C++][Release] Test Flight in
>>> >> >> verify-release-candidate.sh
>>> >> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5054
>>> >> >> >>> > > >
>>> >> >> >>> > > >   * ARROW-5695 [C#][Release] Run sourcelink test in
>>> >> >> >>> > > verify-release-candidate.sh
>>> >> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5695
>>> >> >> >>> > > >
>>> >> >> >>> > > >   * ARROW-4020 [Release] Remove source artifacts from dev dist
>>> >> >> system
>>> >> >> >>> > > after release vote passes
>>> >> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-4020
>>> >> >> >>> > > >
>>> >> >> >>> > > > I marked all of them as Blocker.
>>> >> >> >>> > > >
>>> >> >> >>> > > > It'll take a few days to complete them.
>>> >> >> >>> > > >
>>> >> >> >>> > > > I want to create RC0 when they are completed. Could someone
>>> >> >> >>> > > > work on other Blocker issues while I work on the above
>>> >> >> >>> > > > issues?
>>> >> >> >>> > > >
>>> >> >> >>> > > >
>>> >> >> >>> > > > Thanks,
>>> >> >> >>> > > > --
>>> >> >> >>> > > > kou
>>> >> >> >>> > > >
>>> >> >> >>> > > > In <CAJPUwMDwK6GCANv5s+HKFFRTBXKMg7PZf6RZg=_+
>>> >> >> idyUw+HoLA@mail.gmail.com>
>>> >> >> >>> > > >   "[DISCUSS] Making the Arrow 0.14 release, outstanding items"
>>> >> >> on Fri,
>>> >> >> >>> > > 21 Jun 2019 14:58:54 -0500,
>>> >> >> >>> > > >   Wes McKinney <we...@gmail.com> wrote:
>>> >> >> >>> > > >
>>> >> >> >>> > > > > hi folks,
>>> >> >> >>> > > > >
>>> >> >> >>> > > > > It seems like we are on the home stretch for the 0.14
>>> >> release
>>> >> >> as we
>>> >> >> >>> > > > > have been working intensely to stabilize builds and
>>> >> packaging
>>> >> >> jobs
>>> >> >> >>> > > > > this week and last
>>> >> >> >>> > > > >
>>> >> >> >>> > > > > See status page at
>>> >> >> >>> > > > >
>>> >> >> >>> > > > >
>>> >> >> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
>>> >> >> >>> > > > >
>>> >> >> >>> > > > > I note that there are 64 open issues still, not all of which
>>> >> >> are
>>> >> >> >>> > > > > absolutely necessary to be able to release. If you are a
>>> >> >> stakeholder
>>> >> >> >>> > > > > in any component of the project, can you please:
>>> >> >> >>> > > > >
>>> >> >> >>> > > > > * Remove any issue from the 0.14.0 fix version that you are
>>> >> >> certain
>>> >> >> >>> > > > > will not be resolved in the next week or less
>>> >> >> >>> > > > > * Set to Blocker any issue that you believe must be fixed
>>> >> >> before
>>> >> >> >>> > > releasing
>>> >> >> >>> > > > > * Adding any Blocker issues to the 0.14 Fix Version if not
>>> >> >> there
>>> >> >> >>> > > already
>>> >> >> >>> > > > >
>>> >> >> >>> > > > > In theory we could cut a release candidate sometime next
>>> >> week,
>>> >> >> or in
>>> >> >> >>> > > > > the worst case scenario the week of July 1.
>>> >> >> >>> > > > >
>>> >> >> >>> > > > > If there's anything else that you'd like to discuss on this
>>> >> >> please
>>> >> >> >>> > > > > chime in here.
>>> >> >> >>> > > > >
>>> >> >> >>> > > > > Thanks
>>> >> >> >>> > > > > Wes
>>> >> >> >>> > >
>>> >> >>
>>> >>

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Sutou Kouhei <ko...@clear-code.com>.

Hi,

ursabot doesn't support --arrow-version crossbow.py option.
So I used ursa-labs/crossbow from command line.

Crossbow build: https://github.com/ursa-labs/crossbow/branches/all?utf8=%E2%9C%93&query=build-660

I'll send a release vote e-mail when these builds are
completed and uploads built binaries.

Apache Arrow 0.14.0 RC0 source is already uploaded to
https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-0.14.0-rc0 .

So we can run at least
"dev/release/verify-release-candidate.sh source 0.14.0 0"
before I send a release vote e-mail.


Thanks,
--
kou

In <CA...@mail.gmail.com>
  "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, 28 Jun 2019 16:22:34 -0500,
  Wes McKinney <we...@gmail.com> wrote:

> hi Kou,
> 
> You can already push to https://github.com/ursa-labs/crossbow so I
> think if you use that as your Crossbow queue then you can benefit from
> having the CI systems pre-configured
> 
> On Fri, Jun 28, 2019 at 4:20 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>>
>> Hi Krisztián,
>>
>> OK. I'll use ursabot!
>>
>>
>> Thanks,
>> --
>> kou
>>
>> In <CA...@mail.gmail.com>
>>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, 28 Jun 2019 15:02:32 +0200,
>>   Krisztián Szűcs <sz...@gmail.com> wrote:
>>
>> > @Kou I suggest You to use ursa-labs/crossbow repository for building the
>> > binaries, because the packaging builds are using azure pipelines, travis
>> > and appveyor now. You may setup azure pipelines for your crossbow
>> > instance as well, but it is possibly easier to use ursa-labs' one.
>> > Also You can use the comment mechanism, e.g. opening a PR for the
>> > release branch and using `@ursabot crossbow package -g wheel -g conda -g
>> > linux`.
>> > For dowloading the artifacts You'll still need to clone ursa-labs/crossbow
>> > though.
>> >
>> > On Fri, Jun 28, 2019 at 8:29 AM Sutou Kouhei <ko...@clear-code.com> wrote:
>> >
>> >> Go ahead when a committer says LGTM!
>> >>
>> >> In <CA...@mail.gmail.com>
>> >>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Thu,
>> >> 27 Jun 2019 22:50:35 -0700,
>> >>   Neal Richardson <ne...@gmail.com> wrote:
>> >>
>> >> > I'd like to squeeze https://issues.apache.org/jira/browse/ARROW-5773
>> >> into
>> >> > 0.14 if you'll allow. It's just documentation. I just put the PR up now:
>> >> > https://github.com/apache/arrow/pull/4736
>> >> >
>> >> > Thanks,
>> >> > Neal
>> >> >
>> >> > On Thu, Jun 27, 2019 at 9:55 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>> >> >
>> >> >> We can merge pull request that doesn't change pom.xml for
>> >> >> 0.14.0 until I finished ARROW-4301 and ARROW-5695.
>> >> >>
>> >> >> In <20...@clear-code.com>
>> >> >>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
>> >> Fri,
>> >> >> 28 Jun 2019 13:40:59 +0900 (JST),
>> >> >>   Sutou Kouhei <ko...@clear-code.com> wrote:
>> >> >>
>> >> >> > Thanks!
>> >> >> >
>> >> >> > I'm testing ARROW-4301 (00-prepare.sh) and ARROW-5695
>> >> >> > (verify-release-candidate.sh).
>> >> >> >
>> >> >> > ARROW-4301: We need to build C++ with Gandiva and ORC in
>> >> >> > 00-prepare.sh. I'm working on this.
>> >> >> >
>> >> >> > ARROW-5695: I'll merge this when I confirmed all
>> >> >> > verification patterns are passed with master. I'm running.
>> >> >> >
>> >> >> > I'll create RC0 when I finished them.
>> >> >> >
>> >> >> > For ARROW-5579, please merge it after 0.14.0. I don't want
>> >> >> > to add more pom.xml changes for now.
>> >> >> >
>> >> >> >
>> >> >> > Thanks,
>> >> >> > --
>> >> >> > kou
>> >> >> >
>> >> >> > In <
>> >> CAJPUwMB_he9up4BcvaKTvxaBLuu2uNQwxvn0UWq_VF9aR0H22w@mail.gmail.com>
>> >> >> >   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
>> >> >> Thu, 27 Jun 2019 22:35:45 -0500,
>> >> >> >   Wes McKinney <we...@gmail.com> wrote:
>> >> >> >
>> >> >> >> It looks like we're down to 4 open issues. The remaining items can be
>> >> >> >> merged at Kou's discretion. The one uncertain item is ARROW-5579 --
>> >> >> >> shading Flatbuffers. It seems like it might not be prudent to rush in
>> >> >> >> a patch that might potentially cause problems
>> >> >> >>
>> >> >> >> On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney <we...@gmail.com>
>> >> >> wrote:
>> >> >> >>>
>> >> >> >>> hi folks,
>> >> >> >>>
>> >> >> >>> There are still 10 issues in the 0.14.0 milestone:
>> >> >> >>>
>> >> >> >>> * ARROW-4301: [Java] Patch up, pending review / merge
>> >> >> >>> * ARROW-2104: [C++] Ready to merge pending CI
>> >> >> >>> * ARROW-5500: [R] Ready to merge pending review
>> >> >> >>> * ARROW-5718: [R] Pending review -- may not be necessary for release
>> >> >> >>> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it
>> >> >> >>> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is
>> >> >> >>> working on this in PR now
>> >> >> >>> * ARROW-5695: Patch in review / pending merge
>> >> >> >>> * ARROW-5579: Shading Java Flatbuffers: Pending review
>> >> >> >>> * ARROW-5138: I am looking at this now-ish to determine if a fix is
>> >> in
>> >> >> >>> scope for the release
>> >> >> >>> * ARROW-5497: Publishing R / JS / Java docs -- not essential before
>> >> >> >>> release candidate can be cut
>> >> >> >>>
>> >> >> >>> Is there anything else?
>> >> >> >>>
>> >> >> >>> Based on these outstanding patches I would guess it's going to be
>> >> >> >>> another 12-24 hours from now before an RC can be cut
>> >> >> >>>
>> >> >> >>> I will also spend some time working on the blog post today
>> >> >> >>>
>> >> >> >>> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson
>> >> >> >>> <ne...@gmail.com> wrote:
>> >> >> >>> >
>> >> >> >>> > I've got one of the blockers,
>> >> >> >>> > https://issues.apache.org/jira/browse/ARROW-5497, about the
>> >> >> non-sphinx
>> >> >> >>> > language doc building. I'll spend some time on it this week. It
>> >> >> should get
>> >> >> >>> > done before we're wrapped up with 0.14, but if I get held up, it
>> >> >> doesn't
>> >> >> >>> > need to block making RC0.
>> >> >> >>> >
>> >> >> >>> > In other news, in order to facilitate one of the post-release
>> >> tasks,
>> >> >> I've
>> >> >> >>> > started a google doc for the release announcement blog post:
>> >> >> >>> >
>> >> >>
>> >> https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj
>> >> >> >>> > . While we could wait to deal with the release announcement until
>> >> >> after the
>> >> >> >>> > release happens, doing it early can be a good exercise: it can
>> >> reveal
>> >> >> >>> > details and polishing that are important to realizing the value of
>> >> >> the
>> >> >> >>> > features in the release. Plus, it shouldn't take long and we can
>> >> >> just get
>> >> >> >>> > it out of the way.
>> >> >> >>> >
>> >> >> >>> > For anyone who is a maintainer/stakeholder of one of the
>> >> languages or
>> >> >> >>> > components of the project, please fill in the "notes" section for
>> >> >> your
>> >> >> >>> > component. Others could try to infer what's in the release based
>> >> on
>> >> >> the
>> >> >> >>> > commit messages, but sometimes it's hard to tell what the sum of
>> >> the
>> >> >> parts
>> >> >> >>> > is from that.
>> >> >> >>> >
>> >> >> >>> > Thanks,
>> >> >> >>> > Neal
>> >> >> >>> >
>> >> >> >>> >
>> >> >> >>> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney <wesmckinn@gmail.com
>> >> >
>> >> >> wrote:
>> >> >> >>> >
>> >> >> >>> > > hi Kou,
>> >> >> >>> > >
>> >> >> >>> > > Thank you for volunteering to be the release manager. I think
>> >> many
>> >> >> of
>> >> >> >>> > > the issues marked as Blocker on
>> >> >> >>> > >
>> >> >> >>> > >
>> >> >> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
>> >> >> >>> > >
>> >> >> >>> > > are being actively worked on. I'll follow up with individuals
>> >> >> directly
>> >> >> >>> > > and try to help get patches merged so we can be ready to release
>> >> >> >>> > > ideally before Friday in Japan (end of workday Thursday in the
>> >> >> USA).
>> >> >> >>> > > In certain cases (e.g. ARROW-5335) we may have to accept a
>> >> >> suboptimal
>> >> >> >>> > > solution and do more work for the next release.
>> >> >> >>> > >
>> >> >> >>> > > Thanks
>> >> >> >>> > > Wes
>> >> >> >>> > >
>> >> >> >>> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <
>> >> kou@clear-code.com>
>> >> >> wrote:
>> >> >> >>> > > >
>> >> >> >>> > > > Hi,
>> >> >> >>> > > >
>> >> >> >>> > > > Nobody says "I want to be a release manager". So I'll be the
>> >> >> >>> > > > release manager for 0.14.0.
>> >> >> >>> > > >
>> >> >> >>> > > > I'm working on and assisting some release related issues:
>> >> >> >>> > > >
>> >> >> >>> > > >   * ARROW-5054 [C++][Release] Test Flight in
>> >> >> verify-release-candidate.sh
>> >> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5054
>> >> >> >>> > > >
>> >> >> >>> > > >   * ARROW-5695 [C#][Release] Run sourcelink test in
>> >> >> >>> > > verify-release-candidate.sh
>> >> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5695
>> >> >> >>> > > >
>> >> >> >>> > > >   * ARROW-4020 [Release] Remove source artifacts from dev dist
>> >> >> system
>> >> >> >>> > > after release vote passes
>> >> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-4020
>> >> >> >>> > > >
>> >> >> >>> > > > I marked all of them as Blocker.
>> >> >> >>> > > >
>> >> >> >>> > > > It'll take a few days to complete them.
>> >> >> >>> > > >
>> >> >> >>> > > > I want to create RC0 when they are completed. Could someone
>> >> >> >>> > > > work on other Blocker issues while I work on the above
>> >> >> >>> > > > issues?
>> >> >> >>> > > >
>> >> >> >>> > > >
>> >> >> >>> > > > Thanks,
>> >> >> >>> > > > --
>> >> >> >>> > > > kou
>> >> >> >>> > > >
>> >> >> >>> > > > In <CAJPUwMDwK6GCANv5s+HKFFRTBXKMg7PZf6RZg=_+
>> >> >> idyUw+HoLA@mail.gmail.com>
>> >> >> >>> > > >   "[DISCUSS] Making the Arrow 0.14 release, outstanding items"
>> >> >> on Fri,
>> >> >> >>> > > 21 Jun 2019 14:58:54 -0500,
>> >> >> >>> > > >   Wes McKinney <we...@gmail.com> wrote:
>> >> >> >>> > > >
>> >> >> >>> > > > > hi folks,
>> >> >> >>> > > > >
>> >> >> >>> > > > > It seems like we are on the home stretch for the 0.14
>> >> release
>> >> >> as we
>> >> >> >>> > > > > have been working intensely to stabilize builds and
>> >> packaging
>> >> >> jobs
>> >> >> >>> > > > > this week and last
>> >> >> >>> > > > >
>> >> >> >>> > > > > See status page at
>> >> >> >>> > > > >
>> >> >> >>> > > > >
>> >> >> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
>> >> >> >>> > > > >
>> >> >> >>> > > > > I note that there are 64 open issues still, not all of which
>> >> >> are
>> >> >> >>> > > > > absolutely necessary to be able to release. If you are a
>> >> >> stakeholder
>> >> >> >>> > > > > in any component of the project, can you please:
>> >> >> >>> > > > >
>> >> >> >>> > > > > * Remove any issue from the 0.14.0 fix version that you are
>> >> >> certain
>> >> >> >>> > > > > will not be resolved in the next week or less
>> >> >> >>> > > > > * Set to Blocker any issue that you believe must be fixed
>> >> >> before
>> >> >> >>> > > releasing
>> >> >> >>> > > > > * Adding any Blocker issues to the 0.14 Fix Version if not
>> >> >> there
>> >> >> >>> > > already
>> >> >> >>> > > > >
>> >> >> >>> > > > > In theory we could cut a release candidate sometime next
>> >> week,
>> >> >> or in
>> >> >> >>> > > > > the worst case scenario the week of July 1.
>> >> >> >>> > > > >
>> >> >> >>> > > > > If there's anything else that you'd like to discuss on this
>> >> >> please
>> >> >> >>> > > > > chime in here.
>> >> >> >>> > > > >
>> >> >> >>> > > > > Thanks
>> >> >> >>> > > > > Wes
>> >> >> >>> > >
>> >> >>
>> >>

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Wes McKinney <we...@gmail.com>.

I've made some more additions and edits in

https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#

If anyone would like to fill in some additional information, I can
convert it to Markdown when the time comes next week to publish on the
website

On Fri, Jun 28, 2019 at 4:22 PM Wes McKinney <we...@gmail.com> wrote:
>
> hi Kou,
>
> You can already push to https://github.com/ursa-labs/crossbow so I
> think if you use that as your Crossbow queue then you can benefit from
> having the CI systems pre-configured
>
> On Fri, Jun 28, 2019 at 4:20 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> >
> > Hi Krisztián,
> >
> > OK. I'll use ursabot!
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In <CA...@mail.gmail.com>
> >   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, 28 Jun 2019 15:02:32 +0200,
> >   Krisztián Szűcs <sz...@gmail.com> wrote:
> >
> > > @Kou I suggest You to use ursa-labs/crossbow repository for building the
> > > binaries, because the packaging builds are using azure pipelines, travis
> > > and appveyor now. You may setup azure pipelines for your crossbow
> > > instance as well, but it is possibly easier to use ursa-labs' one.
> > > Also You can use the comment mechanism, e.g. opening a PR for the
> > > release branch and using `@ursabot crossbow package -g wheel -g conda -g
> > > linux`.
> > > For dowloading the artifacts You'll still need to clone ursa-labs/crossbow
> > > though.
> > >
> > > On Fri, Jun 28, 2019 at 8:29 AM Sutou Kouhei <ko...@clear-code.com> wrote:
> > >
> > >> Go ahead when a committer says LGTM!
> > >>
> > >> In <CA...@mail.gmail.com>
> > >>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Thu,
> > >> 27 Jun 2019 22:50:35 -0700,
> > >>   Neal Richardson <ne...@gmail.com> wrote:
> > >>
> > >> > I'd like to squeeze https://issues.apache.org/jira/browse/ARROW-5773
> > >> into
> > >> > 0.14 if you'll allow. It's just documentation. I just put the PR up now:
> > >> > https://github.com/apache/arrow/pull/4736
> > >> >
> > >> > Thanks,
> > >> > Neal
> > >> >
> > >> > On Thu, Jun 27, 2019 at 9:55 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> > >> >
> > >> >> We can merge pull request that doesn't change pom.xml for
> > >> >> 0.14.0 until I finished ARROW-4301 and ARROW-5695.
> > >> >>
> > >> >> In <20...@clear-code.com>
> > >> >>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
> > >> Fri,
> > >> >> 28 Jun 2019 13:40:59 +0900 (JST),
> > >> >>   Sutou Kouhei <ko...@clear-code.com> wrote:
> > >> >>
> > >> >> > Thanks!
> > >> >> >
> > >> >> > I'm testing ARROW-4301 (00-prepare.sh) and ARROW-5695
> > >> >> > (verify-release-candidate.sh).
> > >> >> >
> > >> >> > ARROW-4301: We need to build C++ with Gandiva and ORC in
> > >> >> > 00-prepare.sh. I'm working on this.
> > >> >> >
> > >> >> > ARROW-5695: I'll merge this when I confirmed all
> > >> >> > verification patterns are passed with master. I'm running.
> > >> >> >
> > >> >> > I'll create RC0 when I finished them.
> > >> >> >
> > >> >> > For ARROW-5579, please merge it after 0.14.0. I don't want
> > >> >> > to add more pom.xml changes for now.
> > >> >> >
> > >> >> >
> > >> >> > Thanks,
> > >> >> > --
> > >> >> > kou
> > >> >> >
> > >> >> > In <
> > >> CAJPUwMB_he9up4BcvaKTvxaBLuu2uNQwxvn0UWq_VF9aR0H22w@mail.gmail.com>
> > >> >> >   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
> > >> >> Thu, 27 Jun 2019 22:35:45 -0500,
> > >> >> >   Wes McKinney <we...@gmail.com> wrote:
> > >> >> >
> > >> >> >> It looks like we're down to 4 open issues. The remaining items can be
> > >> >> >> merged at Kou's discretion. The one uncertain item is ARROW-5579 --
> > >> >> >> shading Flatbuffers. It seems like it might not be prudent to rush in
> > >> >> >> a patch that might potentially cause problems
> > >> >> >>
> > >> >> >> On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney <we...@gmail.com>
> > >> >> wrote:
> > >> >> >>>
> > >> >> >>> hi folks,
> > >> >> >>>
> > >> >> >>> There are still 10 issues in the 0.14.0 milestone:
> > >> >> >>>
> > >> >> >>> * ARROW-4301: [Java] Patch up, pending review / merge
> > >> >> >>> * ARROW-2104: [C++] Ready to merge pending CI
> > >> >> >>> * ARROW-5500: [R] Ready to merge pending review
> > >> >> >>> * ARROW-5718: [R] Pending review -- may not be necessary for release
> > >> >> >>> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it
> > >> >> >>> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is
> > >> >> >>> working on this in PR now
> > >> >> >>> * ARROW-5695: Patch in review / pending merge
> > >> >> >>> * ARROW-5579: Shading Java Flatbuffers: Pending review
> > >> >> >>> * ARROW-5138: I am looking at this now-ish to determine if a fix is
> > >> in
> > >> >> >>> scope for the release
> > >> >> >>> * ARROW-5497: Publishing R / JS / Java docs -- not essential before
> > >> >> >>> release candidate can be cut
> > >> >> >>>
> > >> >> >>> Is there anything else?
> > >> >> >>>
> > >> >> >>> Based on these outstanding patches I would guess it's going to be
> > >> >> >>> another 12-24 hours from now before an RC can be cut
> > >> >> >>>
> > >> >> >>> I will also spend some time working on the blog post today
> > >> >> >>>
> > >> >> >>> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson
> > >> >> >>> <ne...@gmail.com> wrote:
> > >> >> >>> >
> > >> >> >>> > I've got one of the blockers,
> > >> >> >>> > https://issues.apache.org/jira/browse/ARROW-5497, about the
> > >> >> non-sphinx
> > >> >> >>> > language doc building. I'll spend some time on it this week. It
> > >> >> should get
> > >> >> >>> > done before we're wrapped up with 0.14, but if I get held up, it
> > >> >> doesn't
> > >> >> >>> > need to block making RC0.
> > >> >> >>> >
> > >> >> >>> > In other news, in order to facilitate one of the post-release
> > >> tasks,
> > >> >> I've
> > >> >> >>> > started a google doc for the release announcement blog post:
> > >> >> >>> >
> > >> >>
> > >> https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj
> > >> >> >>> > . While we could wait to deal with the release announcement until
> > >> >> after the
> > >> >> >>> > release happens, doing it early can be a good exercise: it can
> > >> reveal
> > >> >> >>> > details and polishing that are important to realizing the value of
> > >> >> the
> > >> >> >>> > features in the release. Plus, it shouldn't take long and we can
> > >> >> just get
> > >> >> >>> > it out of the way.
> > >> >> >>> >
> > >> >> >>> > For anyone who is a maintainer/stakeholder of one of the
> > >> languages or
> > >> >> >>> > components of the project, please fill in the "notes" section for
> > >> >> your
> > >> >> >>> > component. Others could try to infer what's in the release based
> > >> on
> > >> >> the
> > >> >> >>> > commit messages, but sometimes it's hard to tell what the sum of
> > >> the
> > >> >> parts
> > >> >> >>> > is from that.
> > >> >> >>> >
> > >> >> >>> > Thanks,
> > >> >> >>> > Neal
> > >> >> >>> >
> > >> >> >>> >
> > >> >> >>> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney <wesmckinn@gmail.com
> > >> >
> > >> >> wrote:
> > >> >> >>> >
> > >> >> >>> > > hi Kou,
> > >> >> >>> > >
> > >> >> >>> > > Thank you for volunteering to be the release manager. I think
> > >> many
> > >> >> of
> > >> >> >>> > > the issues marked as Blocker on
> > >> >> >>> > >
> > >> >> >>> > >
> > >> >> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> > >> >> >>> > >
> > >> >> >>> > > are being actively worked on. I'll follow up with individuals
> > >> >> directly
> > >> >> >>> > > and try to help get patches merged so we can be ready to release
> > >> >> >>> > > ideally before Friday in Japan (end of workday Thursday in the
> > >> >> USA).
> > >> >> >>> > > In certain cases (e.g. ARROW-5335) we may have to accept a
> > >> >> suboptimal
> > >> >> >>> > > solution and do more work for the next release.
> > >> >> >>> > >
> > >> >> >>> > > Thanks
> > >> >> >>> > > Wes
> > >> >> >>> > >
> > >> >> >>> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <
> > >> kou@clear-code.com>
> > >> >> wrote:
> > >> >> >>> > > >
> > >> >> >>> > > > Hi,
> > >> >> >>> > > >
> > >> >> >>> > > > Nobody says "I want to be a release manager". So I'll be the
> > >> >> >>> > > > release manager for 0.14.0.
> > >> >> >>> > > >
> > >> >> >>> > > > I'm working on and assisting some release related issues:
> > >> >> >>> > > >
> > >> >> >>> > > >   * ARROW-5054 [C++][Release] Test Flight in
> > >> >> verify-release-candidate.sh
> > >> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5054
> > >> >> >>> > > >
> > >> >> >>> > > >   * ARROW-5695 [C#][Release] Run sourcelink test in
> > >> >> >>> > > verify-release-candidate.sh
> > >> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5695
> > >> >> >>> > > >
> > >> >> >>> > > >   * ARROW-4020 [Release] Remove source artifacts from dev dist
> > >> >> system
> > >> >> >>> > > after release vote passes
> > >> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-4020
> > >> >> >>> > > >
> > >> >> >>> > > > I marked all of them as Blocker.
> > >> >> >>> > > >
> > >> >> >>> > > > It'll take a few days to complete them.
> > >> >> >>> > > >
> > >> >> >>> > > > I want to create RC0 when they are completed. Could someone
> > >> >> >>> > > > work on other Blocker issues while I work on the above
> > >> >> >>> > > > issues?
> > >> >> >>> > > >
> > >> >> >>> > > >
> > >> >> >>> > > > Thanks,
> > >> >> >>> > > > --
> > >> >> >>> > > > kou
> > >> >> >>> > > >
> > >> >> >>> > > > In <CAJPUwMDwK6GCANv5s+HKFFRTBXKMg7PZf6RZg=_+
> > >> >> idyUw+HoLA@mail.gmail.com>
> > >> >> >>> > > >   "[DISCUSS] Making the Arrow 0.14 release, outstanding items"
> > >> >> on Fri,
> > >> >> >>> > > 21 Jun 2019 14:58:54 -0500,
> > >> >> >>> > > >   Wes McKinney <we...@gmail.com> wrote:
> > >> >> >>> > > >
> > >> >> >>> > > > > hi folks,
> > >> >> >>> > > > >
> > >> >> >>> > > > > It seems like we are on the home stretch for the 0.14
> > >> release
> > >> >> as we
> > >> >> >>> > > > > have been working intensely to stabilize builds and
> > >> packaging
> > >> >> jobs
> > >> >> >>> > > > > this week and last
> > >> >> >>> > > > >
> > >> >> >>> > > > > See status page at
> > >> >> >>> > > > >
> > >> >> >>> > > > >
> > >> >> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> > >> >> >>> > > > >
> > >> >> >>> > > > > I note that there are 64 open issues still, not all of which
> > >> >> are
> > >> >> >>> > > > > absolutely necessary to be able to release. If you are a
> > >> >> stakeholder
> > >> >> >>> > > > > in any component of the project, can you please:
> > >> >> >>> > > > >
> > >> >> >>> > > > > * Remove any issue from the 0.14.0 fix version that you are
> > >> >> certain
> > >> >> >>> > > > > will not be resolved in the next week or less
> > >> >> >>> > > > > * Set to Blocker any issue that you believe must be fixed
> > >> >> before
> > >> >> >>> > > releasing
> > >> >> >>> > > > > * Adding any Blocker issues to the 0.14 Fix Version if not
> > >> >> there
> > >> >> >>> > > already
> > >> >> >>> > > > >
> > >> >> >>> > > > > In theory we could cut a release candidate sometime next
> > >> week,
> > >> >> or in
> > >> >> >>> > > > > the worst case scenario the week of July 1.
> > >> >> >>> > > > >
> > >> >> >>> > > > > If there's anything else that you'd like to discuss on this
> > >> >> please
> > >> >> >>> > > > > chime in here.
> > >> >> >>> > > > >
> > >> >> >>> > > > > Thanks
> > >> >> >>> > > > > Wes
> > >> >> >>> > >
> > >> >>
> > >>

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Wes McKinney <we...@gmail.com>.

hi Kou,

You can already push to https://github.com/ursa-labs/crossbow so I
think if you use that as your Crossbow queue then you can benefit from
having the CI systems pre-configured

On Fri, Jun 28, 2019 at 4:20 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>
> Hi Krisztián,
>
> OK. I'll use ursabot!
>
>
> Thanks,
> --
> kou
>
> In <CA...@mail.gmail.com>
>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, 28 Jun 2019 15:02:32 +0200,
>   Krisztián Szűcs <sz...@gmail.com> wrote:
>
> > @Kou I suggest You to use ursa-labs/crossbow repository for building the
> > binaries, because the packaging builds are using azure pipelines, travis
> > and appveyor now. You may setup azure pipelines for your crossbow
> > instance as well, but it is possibly easier to use ursa-labs' one.
> > Also You can use the comment mechanism, e.g. opening a PR for the
> > release branch and using `@ursabot crossbow package -g wheel -g conda -g
> > linux`.
> > For dowloading the artifacts You'll still need to clone ursa-labs/crossbow
> > though.
> >
> > On Fri, Jun 28, 2019 at 8:29 AM Sutou Kouhei <ko...@clear-code.com> wrote:
> >
> >> Go ahead when a committer says LGTM!
> >>
> >> In <CA...@mail.gmail.com>
> >>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Thu,
> >> 27 Jun 2019 22:50:35 -0700,
> >>   Neal Richardson <ne...@gmail.com> wrote:
> >>
> >> > I'd like to squeeze https://issues.apache.org/jira/browse/ARROW-5773
> >> into
> >> > 0.14 if you'll allow. It's just documentation. I just put the PR up now:
> >> > https://github.com/apache/arrow/pull/4736
> >> >
> >> > Thanks,
> >> > Neal
> >> >
> >> > On Thu, Jun 27, 2019 at 9:55 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> >> >
> >> >> We can merge pull request that doesn't change pom.xml for
> >> >> 0.14.0 until I finished ARROW-4301 and ARROW-5695.
> >> >>
> >> >> In <20...@clear-code.com>
> >> >>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
> >> Fri,
> >> >> 28 Jun 2019 13:40:59 +0900 (JST),
> >> >>   Sutou Kouhei <ko...@clear-code.com> wrote:
> >> >>
> >> >> > Thanks!
> >> >> >
> >> >> > I'm testing ARROW-4301 (00-prepare.sh) and ARROW-5695
> >> >> > (verify-release-candidate.sh).
> >> >> >
> >> >> > ARROW-4301: We need to build C++ with Gandiva and ORC in
> >> >> > 00-prepare.sh. I'm working on this.
> >> >> >
> >> >> > ARROW-5695: I'll merge this when I confirmed all
> >> >> > verification patterns are passed with master. I'm running.
> >> >> >
> >> >> > I'll create RC0 when I finished them.
> >> >> >
> >> >> > For ARROW-5579, please merge it after 0.14.0. I don't want
> >> >> > to add more pom.xml changes for now.
> >> >> >
> >> >> >
> >> >> > Thanks,
> >> >> > --
> >> >> > kou
> >> >> >
> >> >> > In <
> >> CAJPUwMB_he9up4BcvaKTvxaBLuu2uNQwxvn0UWq_VF9aR0H22w@mail.gmail.com>
> >> >> >   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
> >> >> Thu, 27 Jun 2019 22:35:45 -0500,
> >> >> >   Wes McKinney <we...@gmail.com> wrote:
> >> >> >
> >> >> >> It looks like we're down to 4 open issues. The remaining items can be
> >> >> >> merged at Kou's discretion. The one uncertain item is ARROW-5579 --
> >> >> >> shading Flatbuffers. It seems like it might not be prudent to rush in
> >> >> >> a patch that might potentially cause problems
> >> >> >>
> >> >> >> On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney <we...@gmail.com>
> >> >> wrote:
> >> >> >>>
> >> >> >>> hi folks,
> >> >> >>>
> >> >> >>> There are still 10 issues in the 0.14.0 milestone:
> >> >> >>>
> >> >> >>> * ARROW-4301: [Java] Patch up, pending review / merge
> >> >> >>> * ARROW-2104: [C++] Ready to merge pending CI
> >> >> >>> * ARROW-5500: [R] Ready to merge pending review
> >> >> >>> * ARROW-5718: [R] Pending review -- may not be necessary for release
> >> >> >>> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it
> >> >> >>> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is
> >> >> >>> working on this in PR now
> >> >> >>> * ARROW-5695: Patch in review / pending merge
> >> >> >>> * ARROW-5579: Shading Java Flatbuffers: Pending review
> >> >> >>> * ARROW-5138: I am looking at this now-ish to determine if a fix is
> >> in
> >> >> >>> scope for the release
> >> >> >>> * ARROW-5497: Publishing R / JS / Java docs -- not essential before
> >> >> >>> release candidate can be cut
> >> >> >>>
> >> >> >>> Is there anything else?
> >> >> >>>
> >> >> >>> Based on these outstanding patches I would guess it's going to be
> >> >> >>> another 12-24 hours from now before an RC can be cut
> >> >> >>>
> >> >> >>> I will also spend some time working on the blog post today
> >> >> >>>
> >> >> >>> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson
> >> >> >>> <ne...@gmail.com> wrote:
> >> >> >>> >
> >> >> >>> > I've got one of the blockers,
> >> >> >>> > https://issues.apache.org/jira/browse/ARROW-5497, about the
> >> >> non-sphinx
> >> >> >>> > language doc building. I'll spend some time on it this week. It
> >> >> should get
> >> >> >>> > done before we're wrapped up with 0.14, but if I get held up, it
> >> >> doesn't
> >> >> >>> > need to block making RC0.
> >> >> >>> >
> >> >> >>> > In other news, in order to facilitate one of the post-release
> >> tasks,
> >> >> I've
> >> >> >>> > started a google doc for the release announcement blog post:
> >> >> >>> >
> >> >>
> >> https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj
> >> >> >>> > . While we could wait to deal with the release announcement until
> >> >> after the
> >> >> >>> > release happens, doing it early can be a good exercise: it can
> >> reveal
> >> >> >>> > details and polishing that are important to realizing the value of
> >> >> the
> >> >> >>> > features in the release. Plus, it shouldn't take long and we can
> >> >> just get
> >> >> >>> > it out of the way.
> >> >> >>> >
> >> >> >>> > For anyone who is a maintainer/stakeholder of one of the
> >> languages or
> >> >> >>> > components of the project, please fill in the "notes" section for
> >> >> your
> >> >> >>> > component. Others could try to infer what's in the release based
> >> on
> >> >> the
> >> >> >>> > commit messages, but sometimes it's hard to tell what the sum of
> >> the
> >> >> parts
> >> >> >>> > is from that.
> >> >> >>> >
> >> >> >>> > Thanks,
> >> >> >>> > Neal
> >> >> >>> >
> >> >> >>> >
> >> >> >>> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney <wesmckinn@gmail.com
> >> >
> >> >> wrote:
> >> >> >>> >
> >> >> >>> > > hi Kou,
> >> >> >>> > >
> >> >> >>> > > Thank you for volunteering to be the release manager. I think
> >> many
> >> >> of
> >> >> >>> > > the issues marked as Blocker on
> >> >> >>> > >
> >> >> >>> > >
> >> >> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> >> >> >>> > >
> >> >> >>> > > are being actively worked on. I'll follow up with individuals
> >> >> directly
> >> >> >>> > > and try to help get patches merged so we can be ready to release
> >> >> >>> > > ideally before Friday in Japan (end of workday Thursday in the
> >> >> USA).
> >> >> >>> > > In certain cases (e.g. ARROW-5335) we may have to accept a
> >> >> suboptimal
> >> >> >>> > > solution and do more work for the next release.
> >> >> >>> > >
> >> >> >>> > > Thanks
> >> >> >>> > > Wes
> >> >> >>> > >
> >> >> >>> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <
> >> kou@clear-code.com>
> >> >> wrote:
> >> >> >>> > > >
> >> >> >>> > > > Hi,
> >> >> >>> > > >
> >> >> >>> > > > Nobody says "I want to be a release manager". So I'll be the
> >> >> >>> > > > release manager for 0.14.0.
> >> >> >>> > > >
> >> >> >>> > > > I'm working on and assisting some release related issues:
> >> >> >>> > > >
> >> >> >>> > > >   * ARROW-5054 [C++][Release] Test Flight in
> >> >> verify-release-candidate.sh
> >> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5054
> >> >> >>> > > >
> >> >> >>> > > >   * ARROW-5695 [C#][Release] Run sourcelink test in
> >> >> >>> > > verify-release-candidate.sh
> >> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5695
> >> >> >>> > > >
> >> >> >>> > > >   * ARROW-4020 [Release] Remove source artifacts from dev dist
> >> >> system
> >> >> >>> > > after release vote passes
> >> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-4020
> >> >> >>> > > >
> >> >> >>> > > > I marked all of them as Blocker.
> >> >> >>> > > >
> >> >> >>> > > > It'll take a few days to complete them.
> >> >> >>> > > >
> >> >> >>> > > > I want to create RC0 when they are completed. Could someone
> >> >> >>> > > > work on other Blocker issues while I work on the above
> >> >> >>> > > > issues?
> >> >> >>> > > >
> >> >> >>> > > >
> >> >> >>> > > > Thanks,
> >> >> >>> > > > --
> >> >> >>> > > > kou
> >> >> >>> > > >
> >> >> >>> > > > In <CAJPUwMDwK6GCANv5s+HKFFRTBXKMg7PZf6RZg=_+
> >> >> idyUw+HoLA@mail.gmail.com>
> >> >> >>> > > >   "[DISCUSS] Making the Arrow 0.14 release, outstanding items"
> >> >> on Fri,
> >> >> >>> > > 21 Jun 2019 14:58:54 -0500,
> >> >> >>> > > >   Wes McKinney <we...@gmail.com> wrote:
> >> >> >>> > > >
> >> >> >>> > > > > hi folks,
> >> >> >>> > > > >
> >> >> >>> > > > > It seems like we are on the home stretch for the 0.14
> >> release
> >> >> as we
> >> >> >>> > > > > have been working intensely to stabilize builds and
> >> packaging
> >> >> jobs
> >> >> >>> > > > > this week and last
> >> >> >>> > > > >
> >> >> >>> > > > > See status page at
> >> >> >>> > > > >
> >> >> >>> > > > >
> >> >> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> >> >> >>> > > > >
> >> >> >>> > > > > I note that there are 64 open issues still, not all of which
> >> >> are
> >> >> >>> > > > > absolutely necessary to be able to release. If you are a
> >> >> stakeholder
> >> >> >>> > > > > in any component of the project, can you please:
> >> >> >>> > > > >
> >> >> >>> > > > > * Remove any issue from the 0.14.0 fix version that you are
> >> >> certain
> >> >> >>> > > > > will not be resolved in the next week or less
> >> >> >>> > > > > * Set to Blocker any issue that you believe must be fixed
> >> >> before
> >> >> >>> > > releasing
> >> >> >>> > > > > * Adding any Blocker issues to the 0.14 Fix Version if not
> >> >> there
> >> >> >>> > > already
> >> >> >>> > > > >
> >> >> >>> > > > > In theory we could cut a release candidate sometime next
> >> week,
> >> >> or in
> >> >> >>> > > > > the worst case scenario the week of July 1.
> >> >> >>> > > > >
> >> >> >>> > > > > If there's anything else that you'd like to discuss on this
> >> >> please
> >> >> >>> > > > > chime in here.
> >> >> >>> > > > >
> >> >> >>> > > > > Thanks
> >> >> >>> > > > > Wes
> >> >> >>> > >
> >> >>
> >>

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Sutou Kouhei <ko...@clear-code.com>.

Hi Krisztián,

OK. I'll use ursabot!


Thanks,
--
kou

In <CA...@mail.gmail.com>
  "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, 28 Jun 2019 15:02:32 +0200,
  Krisztián Szűcs <sz...@gmail.com> wrote:

> @Kou I suggest You to use ursa-labs/crossbow repository for building the
> binaries, because the packaging builds are using azure pipelines, travis
> and appveyor now. You may setup azure pipelines for your crossbow
> instance as well, but it is possibly easier to use ursa-labs' one.
> Also You can use the comment mechanism, e.g. opening a PR for the
> release branch and using `@ursabot crossbow package -g wheel -g conda -g
> linux`.
> For dowloading the artifacts You'll still need to clone ursa-labs/crossbow
> though.
> 
> On Fri, Jun 28, 2019 at 8:29 AM Sutou Kouhei <ko...@clear-code.com> wrote:
> 
>> Go ahead when a committer says LGTM!
>>
>> In <CA...@mail.gmail.com>
>>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Thu,
>> 27 Jun 2019 22:50:35 -0700,
>>   Neal Richardson <ne...@gmail.com> wrote:
>>
>> > I'd like to squeeze https://issues.apache.org/jira/browse/ARROW-5773
>> into
>> > 0.14 if you'll allow. It's just documentation. I just put the PR up now:
>> > https://github.com/apache/arrow/pull/4736
>> >
>> > Thanks,
>> > Neal
>> >
>> > On Thu, Jun 27, 2019 at 9:55 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>> >
>> >> We can merge pull request that doesn't change pom.xml for
>> >> 0.14.0 until I finished ARROW-4301 and ARROW-5695.
>> >>
>> >> In <20...@clear-code.com>
>> >>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
>> Fri,
>> >> 28 Jun 2019 13:40:59 +0900 (JST),
>> >>   Sutou Kouhei <ko...@clear-code.com> wrote:
>> >>
>> >> > Thanks!
>> >> >
>> >> > I'm testing ARROW-4301 (00-prepare.sh) and ARROW-5695
>> >> > (verify-release-candidate.sh).
>> >> >
>> >> > ARROW-4301: We need to build C++ with Gandiva and ORC in
>> >> > 00-prepare.sh. I'm working on this.
>> >> >
>> >> > ARROW-5695: I'll merge this when I confirmed all
>> >> > verification patterns are passed with master. I'm running.
>> >> >
>> >> > I'll create RC0 when I finished them.
>> >> >
>> >> > For ARROW-5579, please merge it after 0.14.0. I don't want
>> >> > to add more pom.xml changes for now.
>> >> >
>> >> >
>> >> > Thanks,
>> >> > --
>> >> > kou
>> >> >
>> >> > In <
>> CAJPUwMB_he9up4BcvaKTvxaBLuu2uNQwxvn0UWq_VF9aR0H22w@mail.gmail.com>
>> >> >   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
>> >> Thu, 27 Jun 2019 22:35:45 -0500,
>> >> >   Wes McKinney <we...@gmail.com> wrote:
>> >> >
>> >> >> It looks like we're down to 4 open issues. The remaining items can be
>> >> >> merged at Kou's discretion. The one uncertain item is ARROW-5579 --
>> >> >> shading Flatbuffers. It seems like it might not be prudent to rush in
>> >> >> a patch that might potentially cause problems
>> >> >>
>> >> >> On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney <we...@gmail.com>
>> >> wrote:
>> >> >>>
>> >> >>> hi folks,
>> >> >>>
>> >> >>> There are still 10 issues in the 0.14.0 milestone:
>> >> >>>
>> >> >>> * ARROW-4301: [Java] Patch up, pending review / merge
>> >> >>> * ARROW-2104: [C++] Ready to merge pending CI
>> >> >>> * ARROW-5500: [R] Ready to merge pending review
>> >> >>> * ARROW-5718: [R] Pending review -- may not be necessary for release
>> >> >>> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it
>> >> >>> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is
>> >> >>> working on this in PR now
>> >> >>> * ARROW-5695: Patch in review / pending merge
>> >> >>> * ARROW-5579: Shading Java Flatbuffers: Pending review
>> >> >>> * ARROW-5138: I am looking at this now-ish to determine if a fix is
>> in
>> >> >>> scope for the release
>> >> >>> * ARROW-5497: Publishing R / JS / Java docs -- not essential before
>> >> >>> release candidate can be cut
>> >> >>>
>> >> >>> Is there anything else?
>> >> >>>
>> >> >>> Based on these outstanding patches I would guess it's going to be
>> >> >>> another 12-24 hours from now before an RC can be cut
>> >> >>>
>> >> >>> I will also spend some time working on the blog post today
>> >> >>>
>> >> >>> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson
>> >> >>> <ne...@gmail.com> wrote:
>> >> >>> >
>> >> >>> > I've got one of the blockers,
>> >> >>> > https://issues.apache.org/jira/browse/ARROW-5497, about the
>> >> non-sphinx
>> >> >>> > language doc building. I'll spend some time on it this week. It
>> >> should get
>> >> >>> > done before we're wrapped up with 0.14, but if I get held up, it
>> >> doesn't
>> >> >>> > need to block making RC0.
>> >> >>> >
>> >> >>> > In other news, in order to facilitate one of the post-release
>> tasks,
>> >> I've
>> >> >>> > started a google doc for the release announcement blog post:
>> >> >>> >
>> >>
>> https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj
>> >> >>> > . While we could wait to deal with the release announcement until
>> >> after the
>> >> >>> > release happens, doing it early can be a good exercise: it can
>> reveal
>> >> >>> > details and polishing that are important to realizing the value of
>> >> the
>> >> >>> > features in the release. Plus, it shouldn't take long and we can
>> >> just get
>> >> >>> > it out of the way.
>> >> >>> >
>> >> >>> > For anyone who is a maintainer/stakeholder of one of the
>> languages or
>> >> >>> > components of the project, please fill in the "notes" section for
>> >> your
>> >> >>> > component. Others could try to infer what's in the release based
>> on
>> >> the
>> >> >>> > commit messages, but sometimes it's hard to tell what the sum of
>> the
>> >> parts
>> >> >>> > is from that.
>> >> >>> >
>> >> >>> > Thanks,
>> >> >>> > Neal
>> >> >>> >
>> >> >>> >
>> >> >>> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney <wesmckinn@gmail.com
>> >
>> >> wrote:
>> >> >>> >
>> >> >>> > > hi Kou,
>> >> >>> > >
>> >> >>> > > Thank you for volunteering to be the release manager. I think
>> many
>> >> of
>> >> >>> > > the issues marked as Blocker on
>> >> >>> > >
>> >> >>> > >
>> >> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
>> >> >>> > >
>> >> >>> > > are being actively worked on. I'll follow up with individuals
>> >> directly
>> >> >>> > > and try to help get patches merged so we can be ready to release
>> >> >>> > > ideally before Friday in Japan (end of workday Thursday in the
>> >> USA).
>> >> >>> > > In certain cases (e.g. ARROW-5335) we may have to accept a
>> >> suboptimal
>> >> >>> > > solution and do more work for the next release.
>> >> >>> > >
>> >> >>> > > Thanks
>> >> >>> > > Wes
>> >> >>> > >
>> >> >>> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <
>> kou@clear-code.com>
>> >> wrote:
>> >> >>> > > >
>> >> >>> > > > Hi,
>> >> >>> > > >
>> >> >>> > > > Nobody says "I want to be a release manager". So I'll be the
>> >> >>> > > > release manager for 0.14.0.
>> >> >>> > > >
>> >> >>> > > > I'm working on and assisting some release related issues:
>> >> >>> > > >
>> >> >>> > > >   * ARROW-5054 [C++][Release] Test Flight in
>> >> verify-release-candidate.sh
>> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5054
>> >> >>> > > >
>> >> >>> > > >   * ARROW-5695 [C#][Release] Run sourcelink test in
>> >> >>> > > verify-release-candidate.sh
>> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5695
>> >> >>> > > >
>> >> >>> > > >   * ARROW-4020 [Release] Remove source artifacts from dev dist
>> >> system
>> >> >>> > > after release vote passes
>> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-4020
>> >> >>> > > >
>> >> >>> > > > I marked all of them as Blocker.
>> >> >>> > > >
>> >> >>> > > > It'll take a few days to complete them.
>> >> >>> > > >
>> >> >>> > > > I want to create RC0 when they are completed. Could someone
>> >> >>> > > > work on other Blocker issues while I work on the above
>> >> >>> > > > issues?
>> >> >>> > > >
>> >> >>> > > >
>> >> >>> > > > Thanks,
>> >> >>> > > > --
>> >> >>> > > > kou
>> >> >>> > > >
>> >> >>> > > > In <CAJPUwMDwK6GCANv5s+HKFFRTBXKMg7PZf6RZg=_+
>> >> idyUw+HoLA@mail.gmail.com>
>> >> >>> > > >   "[DISCUSS] Making the Arrow 0.14 release, outstanding items"
>> >> on Fri,
>> >> >>> > > 21 Jun 2019 14:58:54 -0500,
>> >> >>> > > >   Wes McKinney <we...@gmail.com> wrote:
>> >> >>> > > >
>> >> >>> > > > > hi folks,
>> >> >>> > > > >
>> >> >>> > > > > It seems like we are on the home stretch for the 0.14
>> release
>> >> as we
>> >> >>> > > > > have been working intensely to stabilize builds and
>> packaging
>> >> jobs
>> >> >>> > > > > this week and last
>> >> >>> > > > >
>> >> >>> > > > > See status page at
>> >> >>> > > > >
>> >> >>> > > > >
>> >> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
>> >> >>> > > > >
>> >> >>> > > > > I note that there are 64 open issues still, not all of which
>> >> are
>> >> >>> > > > > absolutely necessary to be able to release. If you are a
>> >> stakeholder
>> >> >>> > > > > in any component of the project, can you please:
>> >> >>> > > > >
>> >> >>> > > > > * Remove any issue from the 0.14.0 fix version that you are
>> >> certain
>> >> >>> > > > > will not be resolved in the next week or less
>> >> >>> > > > > * Set to Blocker any issue that you believe must be fixed
>> >> before
>> >> >>> > > releasing
>> >> >>> > > > > * Adding any Blocker issues to the 0.14 Fix Version if not
>> >> there
>> >> >>> > > already
>> >> >>> > > > >
>> >> >>> > > > > In theory we could cut a release candidate sometime next
>> week,
>> >> or in
>> >> >>> > > > > the worst case scenario the week of July 1.
>> >> >>> > > > >
>> >> >>> > > > > If there's anything else that you'd like to discuss on this
>> >> please
>> >> >>> > > > > chime in here.
>> >> >>> > > > >
>> >> >>> > > > > Thanks
>> >> >>> > > > > Wes
>> >> >>> > >
>> >>
>>

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Krisztián Szűcs <sz...@gmail.com>.

@Kou I suggest You to use ursa-labs/crossbow repository for building the
binaries, because the packaging builds are using azure pipelines, travis
and appveyor now. You may setup azure pipelines for your crossbow
instance as well, but it is possibly easier to use ursa-labs' one.
Also You can use the comment mechanism, e.g. opening a PR for the
release branch and using `@ursabot crossbow package -g wheel -g conda -g
linux`.
For dowloading the artifacts You'll still need to clone ursa-labs/crossbow
though.

On Fri, Jun 28, 2019 at 8:29 AM Sutou Kouhei <ko...@clear-code.com> wrote:

> Go ahead when a committer says LGTM!
>
> In <CA...@mail.gmail.com>
>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Thu,
> 27 Jun 2019 22:50:35 -0700,
>   Neal Richardson <ne...@gmail.com> wrote:
>
> > I'd like to squeeze https://issues.apache.org/jira/browse/ARROW-5773
> into
> > 0.14 if you'll allow. It's just documentation. I just put the PR up now:
> > https://github.com/apache/arrow/pull/4736
> >
> > Thanks,
> > Neal
> >
> > On Thu, Jun 27, 2019 at 9:55 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> >
> >> We can merge pull request that doesn't change pom.xml for
> >> 0.14.0 until I finished ARROW-4301 and ARROW-5695.
> >>
> >> In <20...@clear-code.com>
> >>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
> Fri,
> >> 28 Jun 2019 13:40:59 +0900 (JST),
> >>   Sutou Kouhei <ko...@clear-code.com> wrote:
> >>
> >> > Thanks!
> >> >
> >> > I'm testing ARROW-4301 (00-prepare.sh) and ARROW-5695
> >> > (verify-release-candidate.sh).
> >> >
> >> > ARROW-4301: We need to build C++ with Gandiva and ORC in
> >> > 00-prepare.sh. I'm working on this.
> >> >
> >> > ARROW-5695: I'll merge this when I confirmed all
> >> > verification patterns are passed with master. I'm running.
> >> >
> >> > I'll create RC0 when I finished them.
> >> >
> >> > For ARROW-5579, please merge it after 0.14.0. I don't want
> >> > to add more pom.xml changes for now.
> >> >
> >> >
> >> > Thanks,
> >> > --
> >> > kou
> >> >
> >> > In <
> CAJPUwMB_he9up4BcvaKTvxaBLuu2uNQwxvn0UWq_VF9aR0H22w@mail.gmail.com>
> >> >   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
> >> Thu, 27 Jun 2019 22:35:45 -0500,
> >> >   Wes McKinney <we...@gmail.com> wrote:
> >> >
> >> >> It looks like we're down to 4 open issues. The remaining items can be
> >> >> merged at Kou's discretion. The one uncertain item is ARROW-5579 --
> >> >> shading Flatbuffers. It seems like it might not be prudent to rush in
> >> >> a patch that might potentially cause problems
> >> >>
> >> >> On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney <we...@gmail.com>
> >> wrote:
> >> >>>
> >> >>> hi folks,
> >> >>>
> >> >>> There are still 10 issues in the 0.14.0 milestone:
> >> >>>
> >> >>> * ARROW-4301: [Java] Patch up, pending review / merge
> >> >>> * ARROW-2104: [C++] Ready to merge pending CI
> >> >>> * ARROW-5500: [R] Ready to merge pending review
> >> >>> * ARROW-5718: [R] Pending review -- may not be necessary for release
> >> >>> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it
> >> >>> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is
> >> >>> working on this in PR now
> >> >>> * ARROW-5695: Patch in review / pending merge
> >> >>> * ARROW-5579: Shading Java Flatbuffers: Pending review
> >> >>> * ARROW-5138: I am looking at this now-ish to determine if a fix is
> in
> >> >>> scope for the release
> >> >>> * ARROW-5497: Publishing R / JS / Java docs -- not essential before
> >> >>> release candidate can be cut
> >> >>>
> >> >>> Is there anything else?
> >> >>>
> >> >>> Based on these outstanding patches I would guess it's going to be
> >> >>> another 12-24 hours from now before an RC can be cut
> >> >>>
> >> >>> I will also spend some time working on the blog post today
> >> >>>
> >> >>> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson
> >> >>> <ne...@gmail.com> wrote:
> >> >>> >
> >> >>> > I've got one of the blockers,
> >> >>> > https://issues.apache.org/jira/browse/ARROW-5497, about the
> >> non-sphinx
> >> >>> > language doc building. I'll spend some time on it this week. It
> >> should get
> >> >>> > done before we're wrapped up with 0.14, but if I get held up, it
> >> doesn't
> >> >>> > need to block making RC0.
> >> >>> >
> >> >>> > In other news, in order to facilitate one of the post-release
> tasks,
> >> I've
> >> >>> > started a google doc for the release announcement blog post:
> >> >>> >
> >>
> https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj
> >> >>> > . While we could wait to deal with the release announcement until
> >> after the
> >> >>> > release happens, doing it early can be a good exercise: it can
> reveal
> >> >>> > details and polishing that are important to realizing the value of
> >> the
> >> >>> > features in the release. Plus, it shouldn't take long and we can
> >> just get
> >> >>> > it out of the way.
> >> >>> >
> >> >>> > For anyone who is a maintainer/stakeholder of one of the
> languages or
> >> >>> > components of the project, please fill in the "notes" section for
> >> your
> >> >>> > component. Others could try to infer what's in the release based
> on
> >> the
> >> >>> > commit messages, but sometimes it's hard to tell what the sum of
> the
> >> parts
> >> >>> > is from that.
> >> >>> >
> >> >>> > Thanks,
> >> >>> > Neal
> >> >>> >
> >> >>> >
> >> >>> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney <wesmckinn@gmail.com
> >
> >> wrote:
> >> >>> >
> >> >>> > > hi Kou,
> >> >>> > >
> >> >>> > > Thank you for volunteering to be the release manager. I think
> many
> >> of
> >> >>> > > the issues marked as Blocker on
> >> >>> > >
> >> >>> > >
> >> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> >> >>> > >
> >> >>> > > are being actively worked on. I'll follow up with individuals
> >> directly
> >> >>> > > and try to help get patches merged so we can be ready to release
> >> >>> > > ideally before Friday in Japan (end of workday Thursday in the
> >> USA).
> >> >>> > > In certain cases (e.g. ARROW-5335) we may have to accept a
> >> suboptimal
> >> >>> > > solution and do more work for the next release.
> >> >>> > >
> >> >>> > > Thanks
> >> >>> > > Wes
> >> >>> > >
> >> >>> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <
> kou@clear-code.com>
> >> wrote:
> >> >>> > > >
> >> >>> > > > Hi,
> >> >>> > > >
> >> >>> > > > Nobody says "I want to be a release manager". So I'll be the
> >> >>> > > > release manager for 0.14.0.
> >> >>> > > >
> >> >>> > > > I'm working on and assisting some release related issues:
> >> >>> > > >
> >> >>> > > >   * ARROW-5054 [C++][Release] Test Flight in
> >> verify-release-candidate.sh
> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5054
> >> >>> > > >
> >> >>> > > >   * ARROW-5695 [C#][Release] Run sourcelink test in
> >> >>> > > verify-release-candidate.sh
> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5695
> >> >>> > > >
> >> >>> > > >   * ARROW-4020 [Release] Remove source artifacts from dev dist
> >> system
> >> >>> > > after release vote passes
> >> >>> > > >     https://issues.apache.org/jira/browse/ARROW-4020
> >> >>> > > >
> >> >>> > > > I marked all of them as Blocker.
> >> >>> > > >
> >> >>> > > > It'll take a few days to complete them.
> >> >>> > > >
> >> >>> > > > I want to create RC0 when they are completed. Could someone
> >> >>> > > > work on other Blocker issues while I work on the above
> >> >>> > > > issues?
> >> >>> > > >
> >> >>> > > >
> >> >>> > > > Thanks,
> >> >>> > > > --
> >> >>> > > > kou
> >> >>> > > >
> >> >>> > > > In <CAJPUwMDwK6GCANv5s+HKFFRTBXKMg7PZf6RZg=_+
> >> idyUw+HoLA@mail.gmail.com>
> >> >>> > > >   "[DISCUSS] Making the Arrow 0.14 release, outstanding items"
> >> on Fri,
> >> >>> > > 21 Jun 2019 14:58:54 -0500,
> >> >>> > > >   Wes McKinney <we...@gmail.com> wrote:
> >> >>> > > >
> >> >>> > > > > hi folks,
> >> >>> > > > >
> >> >>> > > > > It seems like we are on the home stretch for the 0.14
> release
> >> as we
> >> >>> > > > > have been working intensely to stabilize builds and
> packaging
> >> jobs
> >> >>> > > > > this week and last
> >> >>> > > > >
> >> >>> > > > > See status page at
> >> >>> > > > >
> >> >>> > > > >
> >> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> >> >>> > > > >
> >> >>> > > > > I note that there are 64 open issues still, not all of which
> >> are
> >> >>> > > > > absolutely necessary to be able to release. If you are a
> >> stakeholder
> >> >>> > > > > in any component of the project, can you please:
> >> >>> > > > >
> >> >>> > > > > * Remove any issue from the 0.14.0 fix version that you are
> >> certain
> >> >>> > > > > will not be resolved in the next week or less
> >> >>> > > > > * Set to Blocker any issue that you believe must be fixed
> >> before
> >> >>> > > releasing
> >> >>> > > > > * Adding any Blocker issues to the 0.14 Fix Version if not
> >> there
> >> >>> > > already
> >> >>> > > > >
> >> >>> > > > > In theory we could cut a release candidate sometime next
> week,
> >> or in
> >> >>> > > > > the worst case scenario the week of July 1.
> >> >>> > > > >
> >> >>> > > > > If there's anything else that you'd like to discuss on this
> >> please
> >> >>> > > > > chime in here.
> >> >>> > > > >
> >> >>> > > > > Thanks
> >> >>> > > > > Wes
> >> >>> > >
> >>
>

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Sutou Kouhei <ko...@clear-code.com>.

Go ahead when a committer says LGTM!

In <CA...@mail.gmail.com>
  "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Thu, 27 Jun 2019 22:50:35 -0700,
  Neal Richardson <ne...@gmail.com> wrote:

> I'd like to squeeze https://issues.apache.org/jira/browse/ARROW-5773 into
> 0.14 if you'll allow. It's just documentation. I just put the PR up now:
> https://github.com/apache/arrow/pull/4736
> 
> Thanks,
> Neal
> 
> On Thu, Jun 27, 2019 at 9:55 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> 
>> We can merge pull request that doesn't change pom.xml for
>> 0.14.0 until I finished ARROW-4301 and ARROW-5695.
>>
>> In <20...@clear-code.com>
>>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri,
>> 28 Jun 2019 13:40:59 +0900 (JST),
>>   Sutou Kouhei <ko...@clear-code.com> wrote:
>>
>> > Thanks!
>> >
>> > I'm testing ARROW-4301 (00-prepare.sh) and ARROW-5695
>> > (verify-release-candidate.sh).
>> >
>> > ARROW-4301: We need to build C++ with Gandiva and ORC in
>> > 00-prepare.sh. I'm working on this.
>> >
>> > ARROW-5695: I'll merge this when I confirmed all
>> > verification patterns are passed with master. I'm running.
>> >
>> > I'll create RC0 when I finished them.
>> >
>> > For ARROW-5579, please merge it after 0.14.0. I don't want
>> > to add more pom.xml changes for now.
>> >
>> >
>> > Thanks,
>> > --
>> > kou
>> >
>> > In <CA...@mail.gmail.com>
>> >   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
>> Thu, 27 Jun 2019 22:35:45 -0500,
>> >   Wes McKinney <we...@gmail.com> wrote:
>> >
>> >> It looks like we're down to 4 open issues. The remaining items can be
>> >> merged at Kou's discretion. The one uncertain item is ARROW-5579 --
>> >> shading Flatbuffers. It seems like it might not be prudent to rush in
>> >> a patch that might potentially cause problems
>> >>
>> >> On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney <we...@gmail.com>
>> wrote:
>> >>>
>> >>> hi folks,
>> >>>
>> >>> There are still 10 issues in the 0.14.0 milestone:
>> >>>
>> >>> * ARROW-4301: [Java] Patch up, pending review / merge
>> >>> * ARROW-2104: [C++] Ready to merge pending CI
>> >>> * ARROW-5500: [R] Ready to merge pending review
>> >>> * ARROW-5718: [R] Pending review -- may not be necessary for release
>> >>> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it
>> >>> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is
>> >>> working on this in PR now
>> >>> * ARROW-5695: Patch in review / pending merge
>> >>> * ARROW-5579: Shading Java Flatbuffers: Pending review
>> >>> * ARROW-5138: I am looking at this now-ish to determine if a fix is in
>> >>> scope for the release
>> >>> * ARROW-5497: Publishing R / JS / Java docs -- not essential before
>> >>> release candidate can be cut
>> >>>
>> >>> Is there anything else?
>> >>>
>> >>> Based on these outstanding patches I would guess it's going to be
>> >>> another 12-24 hours from now before an RC can be cut
>> >>>
>> >>> I will also spend some time working on the blog post today
>> >>>
>> >>> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson
>> >>> <ne...@gmail.com> wrote:
>> >>> >
>> >>> > I've got one of the blockers,
>> >>> > https://issues.apache.org/jira/browse/ARROW-5497, about the
>> non-sphinx
>> >>> > language doc building. I'll spend some time on it this week. It
>> should get
>> >>> > done before we're wrapped up with 0.14, but if I get held up, it
>> doesn't
>> >>> > need to block making RC0.
>> >>> >
>> >>> > In other news, in order to facilitate one of the post-release tasks,
>> I've
>> >>> > started a google doc for the release announcement blog post:
>> >>> >
>> https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj
>> >>> > . While we could wait to deal with the release announcement until
>> after the
>> >>> > release happens, doing it early can be a good exercise: it can reveal
>> >>> > details and polishing that are important to realizing the value of
>> the
>> >>> > features in the release. Plus, it shouldn't take long and we can
>> just get
>> >>> > it out of the way.
>> >>> >
>> >>> > For anyone who is a maintainer/stakeholder of one of the languages or
>> >>> > components of the project, please fill in the "notes" section for
>> your
>> >>> > component. Others could try to infer what's in the release based on
>> the
>> >>> > commit messages, but sometimes it's hard to tell what the sum of the
>> parts
>> >>> > is from that.
>> >>> >
>> >>> > Thanks,
>> >>> > Neal
>> >>> >
>> >>> >
>> >>> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney <we...@gmail.com>
>> wrote:
>> >>> >
>> >>> > > hi Kou,
>> >>> > >
>> >>> > > Thank you for volunteering to be the release manager. I think many
>> of
>> >>> > > the issues marked as Blocker on
>> >>> > >
>> >>> > >
>> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
>> >>> > >
>> >>> > > are being actively worked on. I'll follow up with individuals
>> directly
>> >>> > > and try to help get patches merged so we can be ready to release
>> >>> > > ideally before Friday in Japan (end of workday Thursday in the
>> USA).
>> >>> > > In certain cases (e.g. ARROW-5335) we may have to accept a
>> suboptimal
>> >>> > > solution and do more work for the next release.
>> >>> > >
>> >>> > > Thanks
>> >>> > > Wes
>> >>> > >
>> >>> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <ko...@clear-code.com>
>> wrote:
>> >>> > > >
>> >>> > > > Hi,
>> >>> > > >
>> >>> > > > Nobody says "I want to be a release manager". So I'll be the
>> >>> > > > release manager for 0.14.0.
>> >>> > > >
>> >>> > > > I'm working on and assisting some release related issues:
>> >>> > > >
>> >>> > > >   * ARROW-5054 [C++][Release] Test Flight in
>> verify-release-candidate.sh
>> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5054
>> >>> > > >
>> >>> > > >   * ARROW-5695 [C#][Release] Run sourcelink test in
>> >>> > > verify-release-candidate.sh
>> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5695
>> >>> > > >
>> >>> > > >   * ARROW-4020 [Release] Remove source artifacts from dev dist
>> system
>> >>> > > after release vote passes
>> >>> > > >     https://issues.apache.org/jira/browse/ARROW-4020
>> >>> > > >
>> >>> > > > I marked all of them as Blocker.
>> >>> > > >
>> >>> > > > It'll take a few days to complete them.
>> >>> > > >
>> >>> > > > I want to create RC0 when they are completed. Could someone
>> >>> > > > work on other Blocker issues while I work on the above
>> >>> > > > issues?
>> >>> > > >
>> >>> > > >
>> >>> > > > Thanks,
>> >>> > > > --
>> >>> > > > kou
>> >>> > > >
>> >>> > > > In <CAJPUwMDwK6GCANv5s+HKFFRTBXKMg7PZf6RZg=_+
>> idyUw+HoLA@mail.gmail.com>
>> >>> > > >   "[DISCUSS] Making the Arrow 0.14 release, outstanding items"
>> on Fri,
>> >>> > > 21 Jun 2019 14:58:54 -0500,
>> >>> > > >   Wes McKinney <we...@gmail.com> wrote:
>> >>> > > >
>> >>> > > > > hi folks,
>> >>> > > > >
>> >>> > > > > It seems like we are on the home stretch for the 0.14 release
>> as we
>> >>> > > > > have been working intensely to stabilize builds and packaging
>> jobs
>> >>> > > > > this week and last
>> >>> > > > >
>> >>> > > > > See status page at
>> >>> > > > >
>> >>> > > > >
>> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
>> >>> > > > >
>> >>> > > > > I note that there are 64 open issues still, not all of which
>> are
>> >>> > > > > absolutely necessary to be able to release. If you are a
>> stakeholder
>> >>> > > > > in any component of the project, can you please:
>> >>> > > > >
>> >>> > > > > * Remove any issue from the 0.14.0 fix version that you are
>> certain
>> >>> > > > > will not be resolved in the next week or less
>> >>> > > > > * Set to Blocker any issue that you believe must be fixed
>> before
>> >>> > > releasing
>> >>> > > > > * Adding any Blocker issues to the 0.14 Fix Version if not
>> there
>> >>> > > already
>> >>> > > > >
>> >>> > > > > In theory we could cut a release candidate sometime next week,
>> or in
>> >>> > > > > the worst case scenario the week of July 1.
>> >>> > > > >
>> >>> > > > > If there's anything else that you'd like to discuss on this
>> please
>> >>> > > > > chime in here.
>> >>> > > > >
>> >>> > > > > Thanks
>> >>> > > > > Wes
>> >>> > >
>>

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Neal Richardson <ne...@gmail.com>.

I'd like to squeeze https://issues.apache.org/jira/browse/ARROW-5773 into
0.14 if you'll allow. It's just documentation. I just put the PR up now:
https://github.com/apache/arrow/pull/4736

Thanks,
Neal

On Thu, Jun 27, 2019 at 9:55 PM Sutou Kouhei <ko...@clear-code.com> wrote:

> We can merge pull request that doesn't change pom.xml for
> 0.14.0 until I finished ARROW-4301 and ARROW-5695.
>
> In <20...@clear-code.com>
>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri,
> 28 Jun 2019 13:40:59 +0900 (JST),
>   Sutou Kouhei <ko...@clear-code.com> wrote:
>
> > Thanks!
> >
> > I'm testing ARROW-4301 (00-prepare.sh) and ARROW-5695
> > (verify-release-candidate.sh).
> >
> > ARROW-4301: We need to build C++ with Gandiva and ORC in
> > 00-prepare.sh. I'm working on this.
> >
> > ARROW-5695: I'll merge this when I confirmed all
> > verification patterns are passed with master. I'm running.
> >
> > I'll create RC0 when I finished them.
> >
> > For ARROW-5579, please merge it after 0.14.0. I don't want
> > to add more pom.xml changes for now.
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In <CA...@mail.gmail.com>
> >   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on
> Thu, 27 Jun 2019 22:35:45 -0500,
> >   Wes McKinney <we...@gmail.com> wrote:
> >
> >> It looks like we're down to 4 open issues. The remaining items can be
> >> merged at Kou's discretion. The one uncertain item is ARROW-5579 --
> >> shading Flatbuffers. It seems like it might not be prudent to rush in
> >> a patch that might potentially cause problems
> >>
> >> On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney <we...@gmail.com>
> wrote:
> >>>
> >>> hi folks,
> >>>
> >>> There are still 10 issues in the 0.14.0 milestone:
> >>>
> >>> * ARROW-4301: [Java] Patch up, pending review / merge
> >>> * ARROW-2104: [C++] Ready to merge pending CI
> >>> * ARROW-5500: [R] Ready to merge pending review
> >>> * ARROW-5718: [R] Pending review -- may not be necessary for release
> >>> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it
> >>> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is
> >>> working on this in PR now
> >>> * ARROW-5695: Patch in review / pending merge
> >>> * ARROW-5579: Shading Java Flatbuffers: Pending review
> >>> * ARROW-5138: I am looking at this now-ish to determine if a fix is in
> >>> scope for the release
> >>> * ARROW-5497: Publishing R / JS / Java docs -- not essential before
> >>> release candidate can be cut
> >>>
> >>> Is there anything else?
> >>>
> >>> Based on these outstanding patches I would guess it's going to be
> >>> another 12-24 hours from now before an RC can be cut
> >>>
> >>> I will also spend some time working on the blog post today
> >>>
> >>> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson
> >>> <ne...@gmail.com> wrote:
> >>> >
> >>> > I've got one of the blockers,
> >>> > https://issues.apache.org/jira/browse/ARROW-5497, about the
> non-sphinx
> >>> > language doc building. I'll spend some time on it this week. It
> should get
> >>> > done before we're wrapped up with 0.14, but if I get held up, it
> doesn't
> >>> > need to block making RC0.
> >>> >
> >>> > In other news, in order to facilitate one of the post-release tasks,
> I've
> >>> > started a google doc for the release announcement blog post:
> >>> >
> https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj
> >>> > . While we could wait to deal with the release announcement until
> after the
> >>> > release happens, doing it early can be a good exercise: it can reveal
> >>> > details and polishing that are important to realizing the value of
> the
> >>> > features in the release. Plus, it shouldn't take long and we can
> just get
> >>> > it out of the way.
> >>> >
> >>> > For anyone who is a maintainer/stakeholder of one of the languages or
> >>> > components of the project, please fill in the "notes" section for
> your
> >>> > component. Others could try to infer what's in the release based on
> the
> >>> > commit messages, but sometimes it's hard to tell what the sum of the
> parts
> >>> > is from that.
> >>> >
> >>> > Thanks,
> >>> > Neal
> >>> >
> >>> >
> >>> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney <we...@gmail.com>
> wrote:
> >>> >
> >>> > > hi Kou,
> >>> > >
> >>> > > Thank you for volunteering to be the release manager. I think many
> of
> >>> > > the issues marked as Blocker on
> >>> > >
> >>> > >
> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> >>> > >
> >>> > > are being actively worked on. I'll follow up with individuals
> directly
> >>> > > and try to help get patches merged so we can be ready to release
> >>> > > ideally before Friday in Japan (end of workday Thursday in the
> USA).
> >>> > > In certain cases (e.g. ARROW-5335) we may have to accept a
> suboptimal
> >>> > > solution and do more work for the next release.
> >>> > >
> >>> > > Thanks
> >>> > > Wes
> >>> > >
> >>> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <ko...@clear-code.com>
> wrote:
> >>> > > >
> >>> > > > Hi,
> >>> > > >
> >>> > > > Nobody says "I want to be a release manager". So I'll be the
> >>> > > > release manager for 0.14.0.
> >>> > > >
> >>> > > > I'm working on and assisting some release related issues:
> >>> > > >
> >>> > > >   * ARROW-5054 [C++][Release] Test Flight in
> verify-release-candidate.sh
> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5054
> >>> > > >
> >>> > > >   * ARROW-5695 [C#][Release] Run sourcelink test in
> >>> > > verify-release-candidate.sh
> >>> > > >     https://issues.apache.org/jira/browse/ARROW-5695
> >>> > > >
> >>> > > >   * ARROW-4020 [Release] Remove source artifacts from dev dist
> system
> >>> > > after release vote passes
> >>> > > >     https://issues.apache.org/jira/browse/ARROW-4020
> >>> > > >
> >>> > > > I marked all of them as Blocker.
> >>> > > >
> >>> > > > It'll take a few days to complete them.
> >>> > > >
> >>> > > > I want to create RC0 when they are completed. Could someone
> >>> > > > work on other Blocker issues while I work on the above
> >>> > > > issues?
> >>> > > >
> >>> > > >
> >>> > > > Thanks,
> >>> > > > --
> >>> > > > kou
> >>> > > >
> >>> > > > In <CAJPUwMDwK6GCANv5s+HKFFRTBXKMg7PZf6RZg=_+
> idyUw+HoLA@mail.gmail.com>
> >>> > > >   "[DISCUSS] Making the Arrow 0.14 release, outstanding items"
> on Fri,
> >>> > > 21 Jun 2019 14:58:54 -0500,
> >>> > > >   Wes McKinney <we...@gmail.com> wrote:
> >>> > > >
> >>> > > > > hi folks,
> >>> > > > >
> >>> > > > > It seems like we are on the home stretch for the 0.14 release
> as we
> >>> > > > > have been working intensely to stabilize builds and packaging
> jobs
> >>> > > > > this week and last
> >>> > > > >
> >>> > > > > See status page at
> >>> > > > >
> >>> > > > >
> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> >>> > > > >
> >>> > > > > I note that there are 64 open issues still, not all of which
> are
> >>> > > > > absolutely necessary to be able to release. If you are a
> stakeholder
> >>> > > > > in any component of the project, can you please:
> >>> > > > >
> >>> > > > > * Remove any issue from the 0.14.0 fix version that you are
> certain
> >>> > > > > will not be resolved in the next week or less
> >>> > > > > * Set to Blocker any issue that you believe must be fixed
> before
> >>> > > releasing
> >>> > > > > * Adding any Blocker issues to the 0.14 Fix Version if not
> there
> >>> > > already
> >>> > > > >
> >>> > > > > In theory we could cut a release candidate sometime next week,
> or in
> >>> > > > > the worst case scenario the week of July 1.
> >>> > > > >
> >>> > > > > If there's anything else that you'd like to discuss on this
> please
> >>> > > > > chime in here.
> >>> > > > >
> >>> > > > > Thanks
> >>> > > > > Wes
> >>> > >
>

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Sutou Kouhei <ko...@clear-code.com>.

We can merge pull request that doesn't change pom.xml for
0.14.0 until I finished ARROW-4301 and ARROW-5695.

In <20...@clear-code.com>
  "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, 28 Jun 2019 13:40:59 +0900 (JST),
  Sutou Kouhei <ko...@clear-code.com> wrote:

> Thanks!
> 
> I'm testing ARROW-4301 (00-prepare.sh) and ARROW-5695
> (verify-release-candidate.sh).
> 
> ARROW-4301: We need to build C++ with Gandiva and ORC in
> 00-prepare.sh. I'm working on this.
> 
> ARROW-5695: I'll merge this when I confirmed all
> verification patterns are passed with master. I'm running.
> 
> I'll create RC0 when I finished them.
> 
> For ARROW-5579, please merge it after 0.14.0. I don't want
> to add more pom.xml changes for now.
> 
> 
> Thanks,
> --
> kou
> 
> In <CA...@mail.gmail.com>
>   "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Thu, 27 Jun 2019 22:35:45 -0500,
>   Wes McKinney <we...@gmail.com> wrote:
> 
>> It looks like we're down to 4 open issues. The remaining items can be
>> merged at Kou's discretion. The one uncertain item is ARROW-5579 --
>> shading Flatbuffers. It seems like it might not be prudent to rush in
>> a patch that might potentially cause problems
>> 
>> On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney <we...@gmail.com> wrote:
>>>
>>> hi folks,
>>>
>>> There are still 10 issues in the 0.14.0 milestone:
>>>
>>> * ARROW-4301: [Java] Patch up, pending review / merge
>>> * ARROW-2104: [C++] Ready to merge pending CI
>>> * ARROW-5500: [R] Ready to merge pending review
>>> * ARROW-5718: [R] Pending review -- may not be necessary for release
>>> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it
>>> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is
>>> working on this in PR now
>>> * ARROW-5695: Patch in review / pending merge
>>> * ARROW-5579: Shading Java Flatbuffers: Pending review
>>> * ARROW-5138: I am looking at this now-ish to determine if a fix is in
>>> scope for the release
>>> * ARROW-5497: Publishing R / JS / Java docs -- not essential before
>>> release candidate can be cut
>>>
>>> Is there anything else?
>>>
>>> Based on these outstanding patches I would guess it's going to be
>>> another 12-24 hours from now before an RC can be cut
>>>
>>> I will also spend some time working on the blog post today
>>>
>>> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson
>>> <ne...@gmail.com> wrote:
>>> >
>>> > I've got one of the blockers,
>>> > https://issues.apache.org/jira/browse/ARROW-5497, about the non-sphinx
>>> > language doc building. I'll spend some time on it this week. It should get
>>> > done before we're wrapped up with 0.14, but if I get held up, it doesn't
>>> > need to block making RC0.
>>> >
>>> > In other news, in order to facilitate one of the post-release tasks, I've
>>> > started a google doc for the release announcement blog post:
>>> > https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj
>>> > . While we could wait to deal with the release announcement until after the
>>> > release happens, doing it early can be a good exercise: it can reveal
>>> > details and polishing that are important to realizing the value of the
>>> > features in the release. Plus, it shouldn't take long and we can just get
>>> > it out of the way.
>>> >
>>> > For anyone who is a maintainer/stakeholder of one of the languages or
>>> > components of the project, please fill in the "notes" section for your
>>> > component. Others could try to infer what's in the release based on the
>>> > commit messages, but sometimes it's hard to tell what the sum of the parts
>>> > is from that.
>>> >
>>> > Thanks,
>>> > Neal
>>> >
>>> >
>>> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney <we...@gmail.com> wrote:
>>> >
>>> > > hi Kou,
>>> > >
>>> > > Thank you for volunteering to be the release manager. I think many of
>>> > > the issues marked as Blocker on
>>> > >
>>> > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
>>> > >
>>> > > are being actively worked on. I'll follow up with individuals directly
>>> > > and try to help get patches merged so we can be ready to release
>>> > > ideally before Friday in Japan (end of workday Thursday in the USA).
>>> > > In certain cases (e.g. ARROW-5335) we may have to accept a suboptimal
>>> > > solution and do more work for the next release.
>>> > >
>>> > > Thanks
>>> > > Wes
>>> > >
>>> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>>> > > >
>>> > > > Hi,
>>> > > >
>>> > > > Nobody says "I want to be a release manager". So I'll be the
>>> > > > release manager for 0.14.0.
>>> > > >
>>> > > > I'm working on and assisting some release related issues:
>>> > > >
>>> > > >   * ARROW-5054 [C++][Release] Test Flight in verify-release-candidate.sh
>>> > > >     https://issues.apache.org/jira/browse/ARROW-5054
>>> > > >
>>> > > >   * ARROW-5695 [C#][Release] Run sourcelink test in
>>> > > verify-release-candidate.sh
>>> > > >     https://issues.apache.org/jira/browse/ARROW-5695
>>> > > >
>>> > > >   * ARROW-4020 [Release] Remove source artifacts from dev dist system
>>> > > after release vote passes
>>> > > >     https://issues.apache.org/jira/browse/ARROW-4020
>>> > > >
>>> > > > I marked all of them as Blocker.
>>> > > >
>>> > > > It'll take a few days to complete them.
>>> > > >
>>> > > > I want to create RC0 when they are completed. Could someone
>>> > > > work on other Blocker issues while I work on the above
>>> > > > issues?
>>> > > >
>>> > > >
>>> > > > Thanks,
>>> > > > --
>>> > > > kou
>>> > > >
>>> > > > In <CA...@mail.gmail.com>
>>> > > >   "[DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri,
>>> > > 21 Jun 2019 14:58:54 -0500,
>>> > > >   Wes McKinney <we...@gmail.com> wrote:
>>> > > >
>>> > > > > hi folks,
>>> > > > >
>>> > > > > It seems like we are on the home stretch for the 0.14 release as we
>>> > > > > have been working intensely to stabilize builds and packaging jobs
>>> > > > > this week and last
>>> > > > >
>>> > > > > See status page at
>>> > > > >
>>> > > > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
>>> > > > >
>>> > > > > I note that there are 64 open issues still, not all of which are
>>> > > > > absolutely necessary to be able to release. If you are a stakeholder
>>> > > > > in any component of the project, can you please:
>>> > > > >
>>> > > > > * Remove any issue from the 0.14.0 fix version that you are certain
>>> > > > > will not be resolved in the next week or less
>>> > > > > * Set to Blocker any issue that you believe must be fixed before
>>> > > releasing
>>> > > > > * Adding any Blocker issues to the 0.14 Fix Version if not there
>>> > > already
>>> > > > >
>>> > > > > In theory we could cut a release candidate sometime next week, or in
>>> > > > > the worst case scenario the week of July 1.
>>> > > > >
>>> > > > > If there's anything else that you'd like to discuss on this please
>>> > > > > chime in here.
>>> > > > >
>>> > > > > Thanks
>>> > > > > Wes
>>> > >

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Sutou Kouhei <ko...@clear-code.com>.

Thanks!

I'm testing ARROW-4301 (00-prepare.sh) and ARROW-5695
(verify-release-candidate.sh).

ARROW-4301: We need to build C++ with Gandiva and ORC in
00-prepare.sh. I'm working on this.

ARROW-5695: I'll merge this when I confirmed all
verification patterns are passed with master. I'm running.

I'll create RC0 when I finished them.

For ARROW-5579, please merge it after 0.14.0. I don't want
to add more pom.xml changes for now.


Thanks,
--
kou

In <CA...@mail.gmail.com>
  "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Thu, 27 Jun 2019 22:35:45 -0500,
  Wes McKinney <we...@gmail.com> wrote:

> It looks like we're down to 4 open issues. The remaining items can be
> merged at Kou's discretion. The one uncertain item is ARROW-5579 --
> shading Flatbuffers. It seems like it might not be prudent to rush in
> a patch that might potentially cause problems
> 
> On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney <we...@gmail.com> wrote:
>>
>> hi folks,
>>
>> There are still 10 issues in the 0.14.0 milestone:
>>
>> * ARROW-4301: [Java] Patch up, pending review / merge
>> * ARROW-2104: [C++] Ready to merge pending CI
>> * ARROW-5500: [R] Ready to merge pending review
>> * ARROW-5718: [R] Pending review -- may not be necessary for release
>> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it
>> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is
>> working on this in PR now
>> * ARROW-5695: Patch in review / pending merge
>> * ARROW-5579: Shading Java Flatbuffers: Pending review
>> * ARROW-5138: I am looking at this now-ish to determine if a fix is in
>> scope for the release
>> * ARROW-5497: Publishing R / JS / Java docs -- not essential before
>> release candidate can be cut
>>
>> Is there anything else?
>>
>> Based on these outstanding patches I would guess it's going to be
>> another 12-24 hours from now before an RC can be cut
>>
>> I will also spend some time working on the blog post today
>>
>> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson
>> <ne...@gmail.com> wrote:
>> >
>> > I've got one of the blockers,
>> > https://issues.apache.org/jira/browse/ARROW-5497, about the non-sphinx
>> > language doc building. I'll spend some time on it this week. It should get
>> > done before we're wrapped up with 0.14, but if I get held up, it doesn't
>> > need to block making RC0.
>> >
>> > In other news, in order to facilitate one of the post-release tasks, I've
>> > started a google doc for the release announcement blog post:
>> > https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj
>> > . While we could wait to deal with the release announcement until after the
>> > release happens, doing it early can be a good exercise: it can reveal
>> > details and polishing that are important to realizing the value of the
>> > features in the release. Plus, it shouldn't take long and we can just get
>> > it out of the way.
>> >
>> > For anyone who is a maintainer/stakeholder of one of the languages or
>> > components of the project, please fill in the "notes" section for your
>> > component. Others could try to infer what's in the release based on the
>> > commit messages, but sometimes it's hard to tell what the sum of the parts
>> > is from that.
>> >
>> > Thanks,
>> > Neal
>> >
>> >
>> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney <we...@gmail.com> wrote:
>> >
>> > > hi Kou,
>> > >
>> > > Thank you for volunteering to be the release manager. I think many of
>> > > the issues marked as Blocker on
>> > >
>> > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
>> > >
>> > > are being actively worked on. I'll follow up with individuals directly
>> > > and try to help get patches merged so we can be ready to release
>> > > ideally before Friday in Japan (end of workday Thursday in the USA).
>> > > In certain cases (e.g. ARROW-5335) we may have to accept a suboptimal
>> > > solution and do more work for the next release.
>> > >
>> > > Thanks
>> > > Wes
>> > >
>> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>> > > >
>> > > > Hi,
>> > > >
>> > > > Nobody says "I want to be a release manager". So I'll be the
>> > > > release manager for 0.14.0.
>> > > >
>> > > > I'm working on and assisting some release related issues:
>> > > >
>> > > >   * ARROW-5054 [C++][Release] Test Flight in verify-release-candidate.sh
>> > > >     https://issues.apache.org/jira/browse/ARROW-5054
>> > > >
>> > > >   * ARROW-5695 [C#][Release] Run sourcelink test in
>> > > verify-release-candidate.sh
>> > > >     https://issues.apache.org/jira/browse/ARROW-5695
>> > > >
>> > > >   * ARROW-4020 [Release] Remove source artifacts from dev dist system
>> > > after release vote passes
>> > > >     https://issues.apache.org/jira/browse/ARROW-4020
>> > > >
>> > > > I marked all of them as Blocker.
>> > > >
>> > > > It'll take a few days to complete them.
>> > > >
>> > > > I want to create RC0 when they are completed. Could someone
>> > > > work on other Blocker issues while I work on the above
>> > > > issues?
>> > > >
>> > > >
>> > > > Thanks,
>> > > > --
>> > > > kou
>> > > >
>> > > > In <CA...@mail.gmail.com>
>> > > >   "[DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri,
>> > > 21 Jun 2019 14:58:54 -0500,
>> > > >   Wes McKinney <we...@gmail.com> wrote:
>> > > >
>> > > > > hi folks,
>> > > > >
>> > > > > It seems like we are on the home stretch for the 0.14 release as we
>> > > > > have been working intensely to stabilize builds and packaging jobs
>> > > > > this week and last
>> > > > >
>> > > > > See status page at
>> > > > >
>> > > > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
>> > > > >
>> > > > > I note that there are 64 open issues still, not all of which are
>> > > > > absolutely necessary to be able to release. If you are a stakeholder
>> > > > > in any component of the project, can you please:
>> > > > >
>> > > > > * Remove any issue from the 0.14.0 fix version that you are certain
>> > > > > will not be resolved in the next week or less
>> > > > > * Set to Blocker any issue that you believe must be fixed before
>> > > releasing
>> > > > > * Adding any Blocker issues to the 0.14 Fix Version if not there
>> > > already
>> > > > >
>> > > > > In theory we could cut a release candidate sometime next week, or in
>> > > > > the worst case scenario the week of July 1.
>> > > > >
>> > > > > If there's anything else that you'd like to discuss on this please
>> > > > > chime in here.
>> > > > >
>> > > > > Thanks
>> > > > > Wes
>> > >

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Wes McKinney <we...@gmail.com>.

It looks like we're down to 4 open issues. The remaining items can be
merged at Kou's discretion. The one uncertain item is ARROW-5579 --
shading Flatbuffers. It seems like it might not be prudent to rush in
a patch that might potentially cause problems

On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney <we...@gmail.com> wrote:
>
> hi folks,
>
> There are still 10 issues in the 0.14.0 milestone:
>
> * ARROW-4301: [Java] Patch up, pending review / merge
> * ARROW-2104: [C++] Ready to merge pending CI
> * ARROW-5500: [R] Ready to merge pending review
> * ARROW-5718: [R] Pending review -- may not be necessary for release
> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it
> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is
> working on this in PR now
> * ARROW-5695: Patch in review / pending merge
> * ARROW-5579: Shading Java Flatbuffers: Pending review
> * ARROW-5138: I am looking at this now-ish to determine if a fix is in
> scope for the release
> * ARROW-5497: Publishing R / JS / Java docs -- not essential before
> release candidate can be cut
>
> Is there anything else?
>
> Based on these outstanding patches I would guess it's going to be
> another 12-24 hours from now before an RC can be cut
>
> I will also spend some time working on the blog post today
>
> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson
> <ne...@gmail.com> wrote:
> >
> > I've got one of the blockers,
> > https://issues.apache.org/jira/browse/ARROW-5497, about the non-sphinx
> > language doc building. I'll spend some time on it this week. It should get
> > done before we're wrapped up with 0.14, but if I get held up, it doesn't
> > need to block making RC0.
> >
> > In other news, in order to facilitate one of the post-release tasks, I've
> > started a google doc for the release announcement blog post:
> > https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj
> > . While we could wait to deal with the release announcement until after the
> > release happens, doing it early can be a good exercise: it can reveal
> > details and polishing that are important to realizing the value of the
> > features in the release. Plus, it shouldn't take long and we can just get
> > it out of the way.
> >
> > For anyone who is a maintainer/stakeholder of one of the languages or
> > components of the project, please fill in the "notes" section for your
> > component. Others could try to infer what's in the release based on the
> > commit messages, but sometimes it's hard to tell what the sum of the parts
> > is from that.
> >
> > Thanks,
> > Neal
> >
> >
> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney <we...@gmail.com> wrote:
> >
> > > hi Kou,
> > >
> > > Thank you for volunteering to be the release manager. I think many of
> > > the issues marked as Blocker on
> > >
> > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> > >
> > > are being actively worked on. I'll follow up with individuals directly
> > > and try to help get patches merged so we can be ready to release
> > > ideally before Friday in Japan (end of workday Thursday in the USA).
> > > In certain cases (e.g. ARROW-5335) we may have to accept a suboptimal
> > > solution and do more work for the next release.
> > >
> > > Thanks
> > > Wes
> > >
> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > Nobody says "I want to be a release manager". So I'll be the
> > > > release manager for 0.14.0.
> > > >
> > > > I'm working on and assisting some release related issues:
> > > >
> > > >   * ARROW-5054 [C++][Release] Test Flight in verify-release-candidate.sh
> > > >     https://issues.apache.org/jira/browse/ARROW-5054
> > > >
> > > >   * ARROW-5695 [C#][Release] Run sourcelink test in
> > > verify-release-candidate.sh
> > > >     https://issues.apache.org/jira/browse/ARROW-5695
> > > >
> > > >   * ARROW-4020 [Release] Remove source artifacts from dev dist system
> > > after release vote passes
> > > >     https://issues.apache.org/jira/browse/ARROW-4020
> > > >
> > > > I marked all of them as Blocker.
> > > >
> > > > It'll take a few days to complete them.
> > > >
> > > > I want to create RC0 when they are completed. Could someone
> > > > work on other Blocker issues while I work on the above
> > > > issues?
> > > >
> > > >
> > > > Thanks,
> > > > --
> > > > kou
> > > >
> > > > In <CA...@mail.gmail.com>
> > > >   "[DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri,
> > > 21 Jun 2019 14:58:54 -0500,
> > > >   Wes McKinney <we...@gmail.com> wrote:
> > > >
> > > > > hi folks,
> > > > >
> > > > > It seems like we are on the home stretch for the 0.14 release as we
> > > > > have been working intensely to stabilize builds and packaging jobs
> > > > > this week and last
> > > > >
> > > > > See status page at
> > > > >
> > > > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> > > > >
> > > > > I note that there are 64 open issues still, not all of which are
> > > > > absolutely necessary to be able to release. If you are a stakeholder
> > > > > in any component of the project, can you please:
> > > > >
> > > > > * Remove any issue from the 0.14.0 fix version that you are certain
> > > > > will not be resolved in the next week or less
> > > > > * Set to Blocker any issue that you believe must be fixed before
> > > releasing
> > > > > * Adding any Blocker issues to the 0.14 Fix Version if not there
> > > already
> > > > >
> > > > > In theory we could cut a release candidate sometime next week, or in
> > > > > the worst case scenario the week of July 1.
> > > > >
> > > > > If there's anything else that you'd like to discuss on this please
> > > > > chime in here.
> > > > >
> > > > > Thanks
> > > > > Wes
> > >

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Wes McKinney <we...@gmail.com>.

hi folks,

There are still 10 issues in the 0.14.0 milestone:

* ARROW-4301: [Java] Patch up, pending review / merge
* ARROW-2104: [C++] Ready to merge pending CI
* ARROW-5500: [R] Ready to merge pending review
* ARROW-5718: [R] Pending review -- may not be necessary for release
* ARROW-5415: [R] No patch yet, but I believe Neal is working on it
* ARROW-5511: [Python] Conda packages with Flight -- Krisztian is
working on this in PR now
* ARROW-5695: Patch in review / pending merge
* ARROW-5579: Shading Java Flatbuffers: Pending review
* ARROW-5138: I am looking at this now-ish to determine if a fix is in
scope for the release
* ARROW-5497: Publishing R / JS / Java docs -- not essential before
release candidate can be cut

Is there anything else?

Based on these outstanding patches I would guess it's going to be
another 12-24 hours from now before an RC can be cut

I will also spend some time working on the blog post today

On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson
<ne...@gmail.com> wrote:
>
> I've got one of the blockers,
> https://issues.apache.org/jira/browse/ARROW-5497, about the non-sphinx
> language doc building. I'll spend some time on it this week. It should get
> done before we're wrapped up with 0.14, but if I get held up, it doesn't
> need to block making RC0.
>
> In other news, in order to facilitate one of the post-release tasks, I've
> started a google doc for the release announcement blog post:
> https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj
> . While we could wait to deal with the release announcement until after the
> release happens, doing it early can be a good exercise: it can reveal
> details and polishing that are important to realizing the value of the
> features in the release. Plus, it shouldn't take long and we can just get
> it out of the way.
>
> For anyone who is a maintainer/stakeholder of one of the languages or
> components of the project, please fill in the "notes" section for your
> component. Others could try to infer what's in the release based on the
> commit messages, but sometimes it's hard to tell what the sum of the parts
> is from that.
>
> Thanks,
> Neal
>
>
> On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney <we...@gmail.com> wrote:
>
> > hi Kou,
> >
> > Thank you for volunteering to be the release manager. I think many of
> > the issues marked as Blocker on
> >
> > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> >
> > are being actively worked on. I'll follow up with individuals directly
> > and try to help get patches merged so we can be ready to release
> > ideally before Friday in Japan (end of workday Thursday in the USA).
> > In certain cases (e.g. ARROW-5335) we may have to accept a suboptimal
> > solution and do more work for the next release.
> >
> > Thanks
> > Wes
> >
> > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> > >
> > > Hi,
> > >
> > > Nobody says "I want to be a release manager". So I'll be the
> > > release manager for 0.14.0.
> > >
> > > I'm working on and assisting some release related issues:
> > >
> > >   * ARROW-5054 [C++][Release] Test Flight in verify-release-candidate.sh
> > >     https://issues.apache.org/jira/browse/ARROW-5054
> > >
> > >   * ARROW-5695 [C#][Release] Run sourcelink test in
> > verify-release-candidate.sh
> > >     https://issues.apache.org/jira/browse/ARROW-5695
> > >
> > >   * ARROW-4020 [Release] Remove source artifacts from dev dist system
> > after release vote passes
> > >     https://issues.apache.org/jira/browse/ARROW-4020
> > >
> > > I marked all of them as Blocker.
> > >
> > > It'll take a few days to complete them.
> > >
> > > I want to create RC0 when they are completed. Could someone
> > > work on other Blocker issues while I work on the above
> > > issues?
> > >
> > >
> > > Thanks,
> > > --
> > > kou
> > >
> > > In <CA...@mail.gmail.com>
> > >   "[DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri,
> > 21 Jun 2019 14:58:54 -0500,
> > >   Wes McKinney <we...@gmail.com> wrote:
> > >
> > > > hi folks,
> > > >
> > > > It seems like we are on the home stretch for the 0.14 release as we
> > > > have been working intensely to stabilize builds and packaging jobs
> > > > this week and last
> > > >
> > > > See status page at
> > > >
> > > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> > > >
> > > > I note that there are 64 open issues still, not all of which are
> > > > absolutely necessary to be able to release. If you are a stakeholder
> > > > in any component of the project, can you please:
> > > >
> > > > * Remove any issue from the 0.14.0 fix version that you are certain
> > > > will not be resolved in the next week or less
> > > > * Set to Blocker any issue that you believe must be fixed before
> > releasing
> > > > * Adding any Blocker issues to the 0.14 Fix Version if not there
> > already
> > > >
> > > > In theory we could cut a release candidate sometime next week, or in
> > > > the worst case scenario the week of July 1.
> > > >
> > > > If there's anything else that you'd like to discuss on this please
> > > > chime in here.
> > > >
> > > > Thanks
> > > > Wes
> >

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Neal Richardson <ne...@gmail.com>.

I've got one of the blockers,
https://issues.apache.org/jira/browse/ARROW-5497, about the non-sphinx
language doc building. I'll spend some time on it this week. It should get
done before we're wrapped up with 0.14, but if I get held up, it doesn't
need to block making RC0.

In other news, in order to facilitate one of the post-release tasks, I've
started a google doc for the release announcement blog post:
https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj
. While we could wait to deal with the release announcement until after the
release happens, doing it early can be a good exercise: it can reveal
details and polishing that are important to realizing the value of the
features in the release. Plus, it shouldn't take long and we can just get
it out of the way.

For anyone who is a maintainer/stakeholder of one of the languages or
components of the project, please fill in the "notes" section for your
component. Others could try to infer what's in the release based on the
commit messages, but sometimes it's hard to tell what the sum of the parts
is from that.

Thanks,
Neal


On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney <we...@gmail.com> wrote:

> hi Kou,
>
> Thank you for volunteering to be the release manager. I think many of
> the issues marked as Blocker on
>
> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
>
> are being actively worked on. I'll follow up with individuals directly
> and try to help get patches merged so we can be ready to release
> ideally before Friday in Japan (end of workday Thursday in the USA).
> In certain cases (e.g. ARROW-5335) we may have to accept a suboptimal
> solution and do more work for the next release.
>
> Thanks
> Wes
>
> On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> >
> > Hi,
> >
> > Nobody says "I want to be a release manager". So I'll be the
> > release manager for 0.14.0.
> >
> > I'm working on and assisting some release related issues:
> >
> >   * ARROW-5054 [C++][Release] Test Flight in verify-release-candidate.sh
> >     https://issues.apache.org/jira/browse/ARROW-5054
> >
> >   * ARROW-5695 [C#][Release] Run sourcelink test in
> verify-release-candidate.sh
> >     https://issues.apache.org/jira/browse/ARROW-5695
> >
> >   * ARROW-4020 [Release] Remove source artifacts from dev dist system
> after release vote passes
> >     https://issues.apache.org/jira/browse/ARROW-4020
> >
> > I marked all of them as Blocker.
> >
> > It'll take a few days to complete them.
> >
> > I want to create RC0 when they are completed. Could someone
> > work on other Blocker issues while I work on the above
> > issues?
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In <CA...@mail.gmail.com>
> >   "[DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri,
> 21 Jun 2019 14:58:54 -0500,
> >   Wes McKinney <we...@gmail.com> wrote:
> >
> > > hi folks,
> > >
> > > It seems like we are on the home stretch for the 0.14 release as we
> > > have been working intensely to stabilize builds and packaging jobs
> > > this week and last
> > >
> > > See status page at
> > >
> > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> > >
> > > I note that there are 64 open issues still, not all of which are
> > > absolutely necessary to be able to release. If you are a stakeholder
> > > in any component of the project, can you please:
> > >
> > > * Remove any issue from the 0.14.0 fix version that you are certain
> > > will not be resolved in the next week or less
> > > * Set to Blocker any issue that you believe must be fixed before
> releasing
> > > * Adding any Blocker issues to the 0.14 Fix Version if not there
> already
> > >
> > > In theory we could cut a release candidate sometime next week, or in
> > > the worst case scenario the week of July 1.
> > >
> > > If there's anything else that you'd like to discuss on this please
> > > chime in here.
> > >
> > > Thanks
> > > Wes
>

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Wes McKinney <we...@gmail.com>.

hi Kou,

Thank you for volunteering to be the release manager. I think many of
the issues marked as Blocker on

https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release

are being actively worked on. I'll follow up with individuals directly
and try to help get patches merged so we can be ready to release
ideally before Friday in Japan (end of workday Thursday in the USA).
In certain cases (e.g. ARROW-5335) we may have to accept a suboptimal
solution and do more work for the next release.

Thanks
Wes

On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>
> Hi,
>
> Nobody says "I want to be a release manager". So I'll be the
> release manager for 0.14.0.
>
> I'm working on and assisting some release related issues:
>
>   * ARROW-5054 [C++][Release] Test Flight in verify-release-candidate.sh
>     https://issues.apache.org/jira/browse/ARROW-5054
>
>   * ARROW-5695 [C#][Release] Run sourcelink test in verify-release-candidate.sh
>     https://issues.apache.org/jira/browse/ARROW-5695
>
>   * ARROW-4020 [Release] Remove source artifacts from dev dist system after release vote passes
>     https://issues.apache.org/jira/browse/ARROW-4020
>
> I marked all of them as Blocker.
>
> It'll take a few days to complete them.
>
> I want to create RC0 when they are completed. Could someone
> work on other Blocker issues while I work on the above
> issues?
>
>
> Thanks,
> --
> kou
>
> In <CA...@mail.gmail.com>
>   "[DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, 21 Jun 2019 14:58:54 -0500,
>   Wes McKinney <we...@gmail.com> wrote:
>
> > hi folks,
> >
> > It seems like we are on the home stretch for the 0.14 release as we
> > have been working intensely to stabilize builds and packaging jobs
> > this week and last
> >
> > See status page at
> >
> > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> >
> > I note that there are 64 open issues still, not all of which are
> > absolutely necessary to be able to release. If you are a stakeholder
> > in any component of the project, can you please:
> >
> > * Remove any issue from the 0.14.0 fix version that you are certain
> > will not be resolved in the next week or less
> > * Set to Blocker any issue that you believe must be fixed before releasing
> > * Adding any Blocker issues to the 0.14 Fix Version if not there already
> >
> > In theory we could cut a release candidate sometime next week, or in
> > the worst case scenario the week of July 1.
> >
> > If there's anything else that you'd like to discuss on this please
> > chime in here.
> >
> > Thanks
> > Wes

Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items

Posted by Sutou Kouhei <ko...@clear-code.com>.

Hi,

Nobody says "I want to be a release manager". So I'll be the
release manager for 0.14.0.

I'm working on and assisting some release related issues:

  * ARROW-5054 [C++][Release] Test Flight in verify-release-candidate.sh
    https://issues.apache.org/jira/browse/ARROW-5054

  * ARROW-5695 [C#][Release] Run sourcelink test in verify-release-candidate.sh
    https://issues.apache.org/jira/browse/ARROW-5695

  * ARROW-4020 [Release] Remove source artifacts from dev dist system after release vote passes 
    https://issues.apache.org/jira/browse/ARROW-4020

I marked all of them as Blocker.

It'll take a few days to complete them.

I want to create RC0 when they are completed. Could someone
work on other Blocker issues while I work on the above
issues?


Thanks,
--
kou

In <CA...@mail.gmail.com>
  "[DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, 21 Jun 2019 14:58:54 -0500,
  Wes McKinney <we...@gmail.com> wrote:

> hi folks,
> 
> It seems like we are on the home stretch for the 0.14 release as we
> have been working intensely to stabilize builds and packaging jobs
> this week and last
> 
> See status page at
> 
> https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release
> 
> I note that there are 64 open issues still, not all of which are
> absolutely necessary to be able to release. If you are a stakeholder
> in any component of the project, can you please:
> 
> * Remove any issue from the 0.14.0 fix version that you are certain
> will not be resolved in the next week or less
> * Set to Blocker any issue that you believe must be fixed before releasing
> * Adding any Blocker issues to the 0.14 Fix Version if not there already
> 
> In theory we could cut a release candidate sometime next week, or in
> the worst case scenario the week of July 1.
> 
> If there's anything else that you'd like to discuss on this please
> chime in here.
> 
> Thanks
> Wes