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+h...@mail.gmail.com>
"[DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, 21 Jun
2019 14:58:54 -0500,
Wes McKinney <[email protected]> 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
