We can merge pull request that doesn't change pom.xml for 0.14.0 until I finished ARROW-4301 and ARROW-5695.
In <[email protected]> "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, 28 Jun 2019 13:40:59 +0900 (JST), Sutou Kouhei <[email protected]> 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_vf9ar0h...@mail.gmail.com> > "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Thu, 27 > Jun 2019 22:35:45 -0500, > Wes McKinney <[email protected]> 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 <[email protected]> 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 >>> <[email protected]> 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 <[email protected]> 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 <[email protected]> >>> > > 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+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 >>> > >
