Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/1203#issuecomment-196529163
Sounds good I will go ahead with doing all of this in subversion, and put
up pull requests in git for release specific docs that we would copy to
subversion when we do a
Github user revans2 closed the pull request at:
https://github.com/apache/storm/pull/1203
---
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 ena
Github user hustfxj commented on the pull request:
https://github.com/apache/storm/pull/1203#issuecomment-195316832
I really support the subversion repo. As far as I am concernedï¼now the
asf-site itself is not convenient for users to browse and learn. And it is
lack of detailed
Github user kishorvpatil commented on the pull request:
https://github.com/apache/storm/pull/1203#issuecomment-195214011
I think this is a good idea. A quick looks suggests, we need to move
document index and other items under it to general non-release specific folder.
(e.g what we se
Github user kishorvpatil commented on the pull request:
https://github.com/apache/storm/pull/1203#issuecomment-195214137
We need to get the links at the bottom fixed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
GitHub user revans2 opened a pull request:
https://github.com/apache/storm/pull/1203
!!! DO NOT MERGE !!! STORM-1617 preview !!! DO NOT MERGE !!!
This is intended to be a preview of STORM-1617. It is by no means done,
but I wanted to get some feedback on this.
Adding in al
