Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/121#issuecomment-62946641
@revans2 Yeah, I created that branch earlier today then got distracted by
meetings before I could send out a notification. That branch is currently
identical to master.
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/121
---
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
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/121#issuecomment-62754593
I think we are at the point where we should merge the security branch into
master. This is a little bit different from most patches/pull requests we have
done, partly
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/121#issuecomment-62758258
I am +1. Feedback on overall security branch we tested it over a period of
time with these merges in with master and there aren't any issues for storm
regular and storm
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/121#issuecomment-62782715
Like I said in the mailing list, I have been out for a few weeks. I didn't
see 0.9.3 go out, but I thought that it must be very close by now. I'll send a
separate mail