Github user srdo commented on the issue:
https://github.com/apache/storm/pull/2117
@erikdw Sorry, didn't get much response on the mailing list thread, so
expected that people just didn't care. I'd be happy with either solution, but
prefer deprecating the existing methods and adding the renamed ones in 1.0.x
and 1.1.x. Then your teams should be able to fix the deprecation warnings when
they have time instead of having to do it immediately.
I don't really feel strongly about it so if you'd prefer going the
suppression route let me know, and I'll do that instead. I'd just like to have
a general rule for how we resolve this type of violation, since it's an issue
in other PRs too (e.g. https://github.com/apache/storm/pull/2146/files)
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
