Github user srdo commented on the issue: https://github.com/apache/storm/pull/2465 @hmcl I don't know that there's a hard rule that it has to be that way, but it seems like a good way to me to ensure that master is the "most fixed"/best state of the code. It's been done this way in the other PRs I've seen. This doesn't apply to patches that fix issues that don't exist in later branches, but this issue isn't one of those.
---