You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by ptgoetz <gi...@git.apache.org> on 2016/01/13 02:34:22 UTC
[GitHub] storm pull request: Merge changes from {master}/docs to {asf-site}
GitHub user ptgoetz opened a pull request:
https://github.com/apache/storm/pull/1008
Merge changes from {master}/docs to {asf-site}
JIRA: https://issues.apache.org/jira/browse/STORM-1468
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptgoetz/storm asf-site
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1008.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 #1008
----
commit d63146b7af0aa4db4af7c5f812ca5358f9395aee
Author: P. Taylor Goetz <pt...@gmail.com>
Date: 2016-01-12T22:31:44Z
update 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: STORM-1468: Merge changes from {master}/docs t...
Posted by revans2 <gi...@git.apache.org>.
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/1008#issuecomment-171331905
I am +1 on this. Not having 2 copies is good and a lot better then what we have now, but I really would prefer to see a hybrid approach. Some documentation is really tied to a release. The REST API for example, where as other documentation is not, the list of contributors and users for example. I really would prefer to see what I see on other sites, which is some common things but they point into release specific sections that are generated from the release branch, and are obviously tied to a release.
We could also use symlinks to denote stable releases vs releases that are no longer supported.
---
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: STORM-1468: Merge changes from {master}/docs t...
Posted by ptgoetz <gi...@git.apache.org>.
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/1008#issuecomment-171126410
Assuming lazy consensus, but would appreciate review in case I missed anything.
---
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: STORM-1468: Merge changes from {master}/docs t...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1008
---
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: STORM-1468: Merge changes from {master}/docs t...
Posted by ptgoetz <gi...@git.apache.org>.
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/1008#issuecomment-171126503
See also #1009
---
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.
---