Apache Thrift 0.12.0 release candidate planning

2018-07-17 Thread Jake Farrell
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

[jira] [Commented] (THRIFT-3950) Memory leak while calling oneway method

2018-07-17 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/THRIFT-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16546839#comment-16546839 ] ASF GitHub Bot commented on THRIFT-3950: jeking3 closed pull request #1568: THRI

[jira] [Resolved] (THRIFT-3950) Memory leak while calling oneway method

2018-07-17 Thread James E. King III (JIRA)
[ https://issues.apache.org/jira/browse/THRIFT-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James E. King III resolved THRIFT-3950. --- Resolution: Fixed Assignee: James E. King III Fix Version/s: 0.12.0

[jira] [Assigned] (THRIFT-4442) release 0.11.0 to https://bintray.com/apache/thrift

2018-07-17 Thread James E. King III (JIRA)
[ https://issues.apache.org/jira/browse/THRIFT-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James E. King III reassigned THRIFT-4442: - Assignee: Jake Farrell > release 0.11.0 to https://bintray.com/apache/thrift >

Re: Apache Thrift 0.12.0 release candidate planning

2018-07-17 Thread James E. King III
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