In that case, I will take my time :) On Mon, Jul 13, 2020 at 11:00 AM Antoine Pitrou <anto...@python.org> wrote:
> > I don't think we want to introduce last-minute unforeseen issues (such > as security issues) in the IPC layer, so personally I'd rather defer the > feature enum implementation to the next version. > > Just my two cents :) > > Regards > > Antoine. > > > Le 13/07/2020 à 19:42, Micah Kornfield a écrit : > > I'll try to make PRs for the feature enum tonight. I don't think this > is a > > blocker as there are other mechanisms to detect the current values > listed. > > > > On Mon, Jul 13, 2020 at 10:37 AM Wes McKinney <wesmck...@gmail.com> > wrote: > > > >> Aside from fixing nightly builds, which of the 25 issues remaining in > >> the 1.0.0 milestone must be resolved in order to release? Speak now or > >> forever hold your peace =) > >> > >> As one problem where I haven't seen activity, we have not implemented > >> the Feature Enum anywhere, do we want to try to add simple > >> implementations in C++ and/or Java? > >> > >> I hope we can cut a release candidate around Wednesday time frame if > >> builds have stabilized. > >> > >> On Thu, Jul 9, 2020 at 3:02 PM Ryan Murray <rym...@dremio.com> wrote: > >>> > >>> I just submitted https://github.com/apache/arrow/pull/7697 to update > >> Docs > >>> for Java type support for 1.0.0, docs probably are not a blocker but > >> should > >>> be an easy review. > >>> > >>> On Thu, Jul 9, 2020 at 7:19 PM Wes McKinney <wesmck...@gmail.com> > wrote: > >>> > >>>> hi David -- I agree with you, I just set ARROW-9265 to a Blocker and > >>>> will spend some time reviewing today. We also need to validate and > >>>> document the expected workflow for PySpark users who upgrade to > >>>> pyarrow=1.x and need to run in a Spark cluster that's using an older > >>>> Arrow Java library > >>>> > >>>> On Thu, Jul 9, 2020 at 12:44 PM David Li <li.david...@gmail.com> > >> wrote: > >>>>> > >>>>> I would submit that https://issues.apache.org/jira/browse/ARROW-9265 > >>>>> and https://issues.apache.org/jira/browse/ARROW-9362 should also be > >>>>> considered blockers, or users are going to have a hard time > >> migrating. > >>>>> Also, without these PRs, no implementation currently actually writes > >>>>> V5 metadata by default. > >>>>> > >>>>> Best, > >>>>> David > >>>>> > >>>>> On 7/9/20, Neal Richardson <neal.p.richard...@gmail.com> wrote: > >>>>>> Hi all, > >>>>>> Following up on this. Are we still on track to cut a release > >> candidate > >>>> on > >>>>>> Monday? > >>>>>> > >>>>>> Some specific calls to action: > >>>>>> > >>>>>> * Looking at the release wiki page ( > >>>>>> > >> https://cwiki.apache.org/confluence/display/ARROW/Arrow+1.0.0+Release > >>>> ), > >>>>>> there are still 58 unstarted issues tagged for 1.0. Half of those > >> are > >>>> Rust > >>>>>> issues that haven't been updated in over a month, so I suspect they > >>>> aren't > >>>>>> going to get resolved this week. Please do review the backlog and > >> bump > >>>> to > >>>>>> 2.0 anything that isn't going to happen now. > >>>>>> > >>>>>> * There are also 5 issues listed as blockers. It's not clear to me > >> that > >>>>>> they're necessarily release blocking, that they're worth holding > >> this > >>>>>> release for, but if you feel strongly that they do and need more > >> time > >>>> to > >>>>>> get them done, please speak up. > >>>>>> > >>>>>> * It appears that the various format changes from the past couple > >> of > >>>> weeks > >>>>>> have gone through, and remaining tasks are not labeled as > >> blockers. If > >>>>>> there is something that you think *should* be considered a blocker, > >>>> please > >>>>>> indicate it as one. > >>>>>> > >>>>>> Neal > >>>>>> > >>>>>> On Thu, Jul 2, 2020 at 1:09 PM Wes McKinney <wesmck...@gmail.com> > >>>> wrote: > >>>>>> > >>>>>>> hi folks, > >>>>>>> > >>>>>>> I hope you and your families are all well. > >>>>>>> > >>>>>>> We're heading into a holiday weekend here in the US -- I would > >> guess > >>>>>>> given the state of the backlog and nightly builds that the > >> earliest we > >>>>>>> could contemplate making the release will be the week of July 13. > >> That > >>>>>>> should give enough time next week to resolve the code changes > >> related > >>>>>>> to the Format votes under way along with other things that come > >> up. > >>>>>>> > >>>>>>> In the meantime, if all stakeholders could please review the 1.0.0 > >>>>>>> backlog and remove issues that you do not believe will be > >> completed in > >>>>>>> the next 10 days with > 0.5 probability, that would be very > >> helpful to > >>>>>>> know where things stand viz-a-viz cutting an RC > >>>>>>> > >>>>>>> Thank you, > >>>>>>> Wes > >>>>>>> > >>>>>>> On Mon, Jun 15, 2020 at 11:21 AM Wes McKinney < > >> wesmck...@gmail.com> > >>>>>>> wrote: > >>>>>>>> > >>>>>>>> hi folks, > >>>>>>>> > >>>>>>>> Based on the previous discussions about release timelines, the > >>>> window > >>>>>>>> for the next major release would be around the week of July 6. > >> Does > >>>>>>>> this sound reasonable? > >>>>>>>> > >>>>>>>> I see that Neal has created a wiki page to help track the > >> burndown > >>>>>>>> > >>>>>>>> > >>>> https://cwiki.apache.org/confluence/display/ARROW/Arrow+1.0.0+Release > >>>>>>>> > >>>>>>>> There are currently 214 issues in the 1.0.0 backlog. Some of > >> these > >>>> are > >>>>>>>> indeed blockers based on the criteria we've indicated for > >> making the > >>>>>>>> 1.0.0 release. Would project stakeholders please review their > >> parts > >>>> of > >>>>>>>> the backlog and remove issues that aren't likely to be > >> completed in > >>>>>>>> the next 21 days? > >>>>>>>> > >>>>>>>> Thanks, > >>>>>>>> Wes > >>>>>>> > >>>>>> > >>>> > >> > > >
