Github user jeking3 commented on the issue:
https://github.com/apache/thrift/pull/1240
In a project I work on that uses thrift, the company maintains a set of
patches they pull (mostly from master, where defects have been fixed on top of
0.10.0) that they need to ship something that works for them. If you need to
change the core exception handling behavior for your project, you can always do
so in your own release engineering workflow regardless of whether a patch gets
accepted and merged upstream. That said, you are always welcome to submit a
patch, certainly. There may be other folks who use thrift who would want the
same option, perhaps for standing up a new service for internal QA and getting
more rapid identification of issues during testing.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
