You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by revans2 <gi...@git.apache.org> on 2016/03/10 22:50:38 UTC
[GitHub] storm pull request: !!! DO NOT MERGE !!! STORM-1617 preview !!! DO...
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 all of the javadocs added in about 88MB. So I am thinking that asf-site itself might need to be in the subversion repo, just so we don't impact all developers with all of the extra files, but I am open to most suggestions.
At this point I have only brought over the javadocs and only put in the 0.10.0 and 0.9.6 releases.
I added in a data file `releases.yaml` that is used to create links to all of the different release sub-directories. If others think this looks OK at a high level, I will start to go through and add in the rest of the release specific docs. Put in the rest of the missing releases. and see if I can put in a permalink, or a sym-link for our current stable release.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/revans2/incubator-storm versioned-site
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1203.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1203
----
commit b12f899b7a1177576035bb0e628622ebda1362d9
Author: Robert (Bobby) Evans <ev...@yahoo-inc.com>
Date: 2016-03-10T18:54:58Z
Soem cleanup
commit 0140297c0f7f8cc081008bdecce5c7dc8f00a8fa
Author: Robert (Bobby) Evans <ev...@yahoo-inc.com>
Date: 2016-03-10T18:57:14Z
Config issue
commit 47fe62e75c91649d85afd6dcaf6a6170562e6627
Author: Robert (Bobby) Evans <ev...@yahoo-inc.com>
Date: 2016-03-10T20:30:22Z
Checkpoint
commit d3d7e87bac0b4fbf417a12ae0cc16742a5f6588a
Author: Robert (Bobby) Evans <ev...@yahoo-inc.com>
Date: 2016-03-10T20:53:06Z
A few more things updated to make this work
commit c5d8dc938e835c1ec93680886060c4f53574cb9c
Author: Robert (Bobby) Evans <ev...@yahoo-inc.com>
Date: 2016-03-10T20:56:58Z
Added in 0.9.6 javadocs
commit 5a8e4e78f325eea6a60cda962e97b0287bfc9b8f
Author: Robert (Bobby) Evans <ev...@yahoo-inc.com>
Date: 2016-03-10T21:08:25Z
Updated header to point to proper pages
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: !!! DO NOT MERGE !!! STORM-1617 preview !!! DO...
Posted by hustfxj <gi...@git.apache.org>.
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 documentation .
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: !!! DO NOT MERGE !!! STORM-1617 preview !!! DO...
Posted by kishorvpatil <gi...@git.apache.org>.
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 see in the first look at the bottom.)
Documentation index can be at the top link as general documentation.
Also, I see some duplication in http://storm.apache.org/documentation.html#integration and http://storm.apache.org/about/integrates.html
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: !!! DO NOT MERGE !!! STORM-1617 preview !!! DO...
Posted by kishorvpatil <gi...@git.apache.org>.
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 your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: !!! DO NOT MERGE !!! STORM-1617 preview !!! DO...
Posted by revans2 <gi...@git.apache.org>.
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 release.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: !!! DO NOT MERGE !!! STORM-1617 preview !!! DO...
Posted by revans2 <gi...@git.apache.org>.
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---