[
https://issues.apache.org/jira/browse/THRIFT-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16294980#comment-16294980
]
Christopher Tubbs commented on THRIFT-4250:
-------------------------------------------
[~jensg]. I'm finding it difficult to answer your question. I believe it is
framed incorrectly for at least two reasons:
# I did not claim there were breaking changes, only that there was more
potential for breaking changes in the set of 270 (previously incorrectly said
170) than the removal of a debug statement, and
# Even if there were any such breaking changes, I would never have claimed that
it prevented me from using 0.11.0. Historically, breaking changes in Thrift
have (usually) not prevented me from using them... such breakages have usually
only required patching the client in incompatible ways.
But, neither of these were the point of my comment. The point of my comment was
to suggest that this was a poor way for the Thrift developers to interact with
their community, and to suggest a better way of interacting on JIRA (see my
concluding: "What should have happened..." sentence above).
> 0.11.0 release candidate (was: Please release 0.10.1 with fix for THRIFT-4062)
> ------------------------------------------------------------------------------
>
> Key: THRIFT-4250
> URL: https://issues.apache.org/jira/browse/THRIFT-4250
> Project: Thrift
> Issue Type: Wish
> Components: Build Process
> Affects Versions: 0.10.0
> Reporter: David Ross
> Assignee: Jens Geyer
> Labels: performance, release
> Fix For: 0.11.0
>
>
> THRIFT-4062 is a serious usability issue for anyone running nontrivial java
> applications with thrift. It was fixed months ago. I am requesting a patch
> release on the 0.10.0 with, potentially, only this one commit.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
