That sounds great to me. I'll make sure I'm able to build and sign artifacts this week and surface any issues I find along the way. Looking forward to a smooth release!
On Tue, Jul 24, 2018 at 11:24 AM Wes McKinney <wesmck...@gmail.com> wrote: > hi folks, > > Tuesday's update: it looks like we're going to be able to close out > the C++ and Python dev work without any issues before the end of the > week. I'm going to make some tweaks to the website per the JIRAs that > are available but that won't take long. > > The two items where there's some uncertainty: > > * Packaging: we need the PMC member who is going to conduct the > release vote (Phillip C?) to validate the packaging workflow so we > don't get burned at the last minute and have to do multiple RCs > * ARROW-2704 (https://github.com/apache/arrow/pull/2139): As I > commented there I think we need to set some kind of hard deadline like > EOD Friday to reach a merge-ready patch > > Rather than try to rush out an RC before end of the week, Sunday or > Monday would be a good day to cut it assuming the above items are > looking good. > > Any other thoughts? > > Thanks > Wes > > On Mon, Jul 23, 2018 at 11:47 PM, Craig Ching <craigch...@gmail.com> > wrote: > > Wes and Li, > > > > Thanks for your patience, and sorry for the noise! I did have an apache > > jira account, but it's been captured by a previous employer. I have > > created a new account and I can see the jira page now. Thanks! > > > > Cheers, > > Craig > > > > On Mon, Jul 23, 2018 at 10:18 PM Wes McKinney <wesmck...@gmail.com> > wrote: > > > >> hi Craig -- do you have a JIRA account? I think that page should be > >> visible to all logged in JIRA users. Let me know if not. > >> > >> - Wes > >> > >> On Mon, Jul 23, 2018 at 10:48 PM, Craig Ching <craigch...@gmail.com> > >> wrote: > >> > Thanks for this, Wes, I appreciate it! > >> > > >> > On Mon, Jul 23, 2018 at 8:16 PM Wes McKinney <wesmck...@gmail.com> > >> wrote: > >> > > >> >> You can also have a look at > >> >> > >> >> > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.10.0+Release > >> >> > >> >> On Mon, Jul 23, 2018 at 8:40 PM, Li Jin <ice.xell...@gmail.com> > wrote: > >> >> > Craig, > >> >> > > >> >> > If you click the link > >> >> > https://issues.apache.org/jira/projects/ARROW/versions/12342562 > you > >> can > >> >> > view issues under "issues in progress" and "issues to do" > >> >> > > >> >> > On Mon, Jul 23, 2018 at 8:30 PM, Craig Ching <craigch...@gmail.com > > > >> >> wrote: > >> >> > > >> >> >> Hi Li, > >> >> >> > >> >> >> Is there a better link to see the 16 issues required for 0.10 to > be > >> >> >> released? > >> >> >> > >> >> >> Cheers, > >> >> >> Craig > >> >> >> > >> >> >> On Mon, Jul 23, 2018 at 5:47 PM Li Jin <ice.xell...@gmail.com> > >> wrote: > >> >> >> > >> >> >> > Sounds good. I will stand by now. > >> >> >> > > >> >> >> > On Mon, Jul 23, 2018 at 1:40 PM, Wes McKinney < > wesmck...@gmail.com > >> > > >> >> >> wrote: > >> >> >> > > >> >> >> > > hi Li -- thanks. We are working on these issues; I will report > >> in on > >> >> >> > > the status at the end of the week. If anything is C++/Python > or > >> >> >> > > Website-related, please don't move anything out of the > milestone > >> >> >> > > without checking with me. > >> >> >> > > > >> >> >> > > The most at risk JIRA for the 0.10 release AFAICT is > ARROW-2704: > >> >> >> > > https://github.com/apache/arrow/pull/2139. I have been > following > >> >> the > >> >> >> > > code review; there seems to be a good deal of cross talk and > >> >> >> > > disagreement. > >> >> >> > > > >> >> >> > > - Wes > >> >> >> > > > >> >> >> > > On Mon, Jul 23, 2018 at 1:25 PM, Li Jin < > ice.xell...@gmail.com> > >> >> wrote: > >> >> >> > > > Hi All, > >> >> >> > > > > >> >> >> > > > As we get close to cut 0.10.0 release candidate, I want to > >> clean > >> >> up > >> >> >> the > >> >> >> > > > remaining 16 open issues. Here is the board: > >> >> >> > > > > >> >> >> > > > > >> https://issues.apache.org/jira/projects/ARROW/versions/12342562 > >> >> >> > > > > >> >> >> > > > For the two with PR open, I'd assume we can include them in > the > >> >> >> release > >> >> >> > > > once review is finished. > >> >> >> > > > > >> >> >> > > > For the rest 14, if you think any of those should be > blocker to > >> >> the > >> >> >> > > > release, please comment so I can track progress, otherwise > I'd > >> >> assume > >> >> >> > > they > >> >> >> > > > are not in 0.10 and will remove them from 0.10 by the end of > >> the > >> >> >> week. > >> >> >> > > > > >> >> >> > > > Thank you, > >> >> >> > > > Li > >> >> >> > > > >> >> >> > > >> >> >> > >> >> > >> >
