The biggest CI issue I have seen is that the builds fail more often in Common Lisp than anywhere else. It looks as if CL is losing track of a temporary file that it creates. Perhaps it's a race, I don't know. With the new control we have over CI I can rekick any build job and eventually it will pass, but that is a pain, and only admins can do it.
I would like to see the release note generation enhanced to group issues together by component AND THEN by type. I think that will be a lot more useful to people reading them. I think I will be able to provide a fix for the long-standing C++ side HTTP transport issues we've been seeing relative to some of the work I have been doing at work for message bus support, but it's not ready yet so it'll have to go into another release. Currently open issues that are labeled BLOCKER: THRIFT-4180 (Impossible to build Thrift C++ library for Android (NDK)) There are 32 critical ones. We need a real serious and tough backlog scrub... - Jim On Tue, Jul 17, 2018 at 11:59 AM Jake Farrell <[email protected]> wrote: > I would like to start the planning for our next release candidate, 0.12.0 > RC, and wanted to open up the discussion for any blocking issues that we > would like to see make it in before cutting the branch and addressing any > outstanding CI issues. Thoughts? > > -Jake >
