I disagree. I think we need a forcing function to create some urgency to work out any of the problems that may come up. If we need to make a 0.13.1 to fix problems that are not caught during the release (and producing binary artifacts) then I think that is okay
On Tue, Mar 12, 2019 at 9:53 AM Krisztián Szűcs <szucs.kriszt...@gmail.com> wrote: > > Hi, > > The CMake refactor is huge enough to cause unexpected post-release > defects. I'd consider shipping it with the next release and let is stabilize > during the development of 0.14. > > > On Tue, Mar 12, 2019 at 3:41 PM Wes McKinney <wesmck...@gmail.com> wrote: > > > hi Uwe, > > > > I would be OK with trying to release next week. Let's see what others > > think. Getting the CMake refactor in and packaging sorted out is the > > big priority for the C++-using ecosystem. I haven't seen anything > > hugely pressing in the other impls based on the recent patch flow. > > Having C# NuGet package working would be nice > > > > - Wes > > > > On Tue, Mar 12, 2019 at 9:37 AM Uwe L. Korn <uw...@xhochy.com> wrote: > > > > > > Hello, > > > > > > two things come to my mind: > > > > > > * I'm spending now some time again on the CMake refactor. The only > > blocker I currently see is the issue with detecting the correct gtest > > libraries on Windows. Otherwise this can go in. Being very confident about > > my work: This will break things even though CI is green. A safer bet from > > my side would be to make a release and then merge once the release vote > > passed. I would then like to aim for a shorter cycle for 0.14 to get this > > working and green as a lot of the refactor is needed to get packages into > > distributions and thus also clear a bit the path for the availablity of an > > R package for arrow. > > > * I could also volunteer to be RM *if we do the release process > > starting March 18*. I have limited time the week after but enough spare to > > make a release in the week of March 18. > > > > > > Uwe > > > > > > On Tue, Mar 12, 2019, at 3:21 PM, Wes McKinney wrote: > > > > hi folks, > > > > > > > > I think we are on track to be able to release toward the end of this > > > > month. My proposed timeline: > > > > > > > > * This week (March 11-15): feature/improvement push mostly > > > > * Next week (March 18-22): shift to bug fixes, stabilization, empty > > > > backlog of feature/improvement JIRAs > > > > * Week of March 25: propose release candidate > > > > > > > > Does this seem reasonable? This puts us at about 9-10 weeks from 0.12. > > > > > > > > We need an RM for 0.13, any PMCs want to volunteer? > > > > > > > > Take a look at our release page: > > > > > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103091219 > > > > > > > > Out of the open or in-progress issues, we have: > > > > > > > > * C#: 3 issues > > > > * C++ (all components): 51 issues > > > > * Java: 3 issues > > > > * Python: 38 issues > > > > * Rust (all components): 33 issues > > > > > > > > Please help curating the backlogs for each component. There's a > > > > smattering of issues in other categories. There are also 10 open > > > > issues with No Component (and 20 resolved issues), those need their > > > > metadata fixed. > > > > > > > > Thanks, > > > > Wes > > > > > > > > On Wed, Feb 27, 2019 at 1:49 PM Wes McKinney <wesmck...@gmail.com> > > wrote: > > > > > > > > > > The timeline for the 0.13 release is drawing closer. I would say we > > > > > should consider a release candidate either the week of March 18 or > > > > > March 25, which gives us ~3 weeks to close out backlog items. > > > > > > > > > > There are around 220 issues open or in-progress in > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.13.0+Release > > > > > > > > > > Please have a look. If issues are not assigned to someone as the next > > > > > couple of weeks pass by I'll begin moving at least C++ and Python > > > > > issues to 0.14 that don't seem like they're going to get done for > > > > > 0.13. If development stakeholders for C#, Java, Rust, Ruby, and other > > > > > components can review and curate the issues that would be helpful. > > > > > > > > > > You can help keep the JIRA issues tidy by making sure to add Fix > > > > > Version to issues and to make sure to add a Component so that issues > > > > > are properly categorized in the release notes. > > > > > > > > > > Thanks > > > > > Wes > > > > > > > > > > On Sat, Feb 9, 2019 at 10:39 AM Wes McKinney <wesmck...@gmail.com> > > wrote: > > > > > > > > > > > > See > > https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide > > > > > > > > > > > > The source release step is one of the places where problems occur. > > > > > > > > > > > > On Sat, Feb 9, 2019, 10:33 AM <ane...@quiltdata.io wrote: > > > > > >> > > > > > >> > > > > > >> > On Feb 8, 2019, at 9:19 AM, Uwe L. Korn <m...@uwekorn.com> > > wrote: > > > > > >> > > > > > > >> > We could dockerize some of the release steps to ensure that > > they run in the same environment. > > > > > >> > > > > > >> I may be able to help with said Dockerization. If not for this > > release, then for the next. Are there docs on which systems we wish to > > target and/or any build steps beyond the current dev container ( > > https://github.com/apache/arrow/tree/master/dev/container)? > > > > > >
