[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374066#comment-15374066 ] Julian Hyde commented on EAGLE-371: --- Thanks for logging this case, [~yonzhang2012]. Have you considered combining the web site with the documentation? You could put this into a directory of your source code (not a branch), or you could create a new git repo (hosted under apache.org, and mirrored under github.com/apache). > remove eagle-docs from develop branch > - > > Key: EAGLE-371 > URL: https://issues.apache.org/jira/browse/EAGLE-371 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.5 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Trivial > Fix For: 0.5 > > > eagle-docs will be maintained in > https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't > need maintain duplicated documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374047#comment-15374047 ] Edward Zhang commented on EAGLE-371: We tried with Eagle branch https://github.com/apache/incubator-eagle/tree/document long time ago, and will officially move all documents to this branch in Eagle 0.5. Use https://issues.apache.org/jira/browse/EAGLE-373 to track > remove eagle-docs from develop branch > - > > Key: EAGLE-371 > URL: https://issues.apache.org/jira/browse/EAGLE-371 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.5 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Trivial > Fix For: 0.5 > > > eagle-docs will be maintained in > https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't > need maintain duplicated documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372034#comment-15372034 ] Julian Hyde commented on EAGLE-371: --- The ASF cannot guarantee the hygiene of Eagle's IP (and yes, documentation is part of the IP) if it is not managed on ASF hardware. A github MIRROR of the ASF git under github.com/apache/incubator-eagle is OK, but Eagle should be moving away from https://github.com/eaglemonitoring as fast as possible. Also, maybe I missed the discussion, but it sounds as if this decision was made off-list. If it's not possible to move off of https://github.com/eaglemonitoring immediately, let's at least create some JIRA cases so that we know where we are heading. > remove eagle-docs from develop branch > - > > Key: EAGLE-371 > URL: https://issues.apache.org/jira/browse/EAGLE-371 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.5 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Trivial > Fix For: 0.5 > > > eagle-docs will be maintained in > https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't > need maintain duplicated documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372026#comment-15372026 ] Edward Zhang commented on EAGLE-371: [~julianhyde]maybe your concern is we should maintain eagle documents in apache git. If that is the concern, today eagle does not maintain document in apache git. We may need do that in eagle 0.5 when we have document maintained in one branch of apache git > remove eagle-docs from develop branch > - > > Key: EAGLE-371 > URL: https://issues.apache.org/jira/browse/EAGLE-371 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.5 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Trivial > Fix For: 0.5 > > > eagle-docs will be maintained in > https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't > need maintain duplicated documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372017#comment-15372017 ] Edward Zhang commented on EAGLE-371: [~julianhyde] we have eagle document well maintained in https://github.com/eaglemonitoring/eaglemonitoring.github.io, and the URL http://eagle.incubator.apache.org/docs still remains the same. This is a temporary solution, and we want to move all documents into one branch of eagle github but not embedded together with source code. We look at many projects in terms of document lifecycle management, for Eagle we want to use branch to manage eagle doc. And document differences between different eagle releases are maintained in eagle eagle release if we want to keep old document. > remove eagle-docs from develop branch > - > > Key: EAGLE-371 > URL: https://issues.apache.org/jira/browse/EAGLE-371 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.5 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Trivial > Fix For: 0.5 > > > eagle-docs will be maintained in > https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't > need maintain duplicated documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372004#comment-15372004 ] Julian Hyde commented on EAGLE-371: --- Does this mean that eagle-docs are being removed from Apache git? That doesn't sound good. Also, what is the URL where the documents are being published? Does that remain http://eagle.incubator.apache.org/docs? > remove eagle-docs from develop branch > - > > Key: EAGLE-371 > URL: https://issues.apache.org/jira/browse/EAGLE-371 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.5 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Trivial > Fix For: 0.5 > > > eagle-docs will be maintained in > https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't > need maintain duplicated documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371980#comment-15371980 ] ASF GitHub Bot commented on EAGLE-371: -- Github user yonzhang commented on the issue: https://github.com/apache/incubator-eagle/pull/263 merged > remove eagle-docs from develop branch > - > > Key: EAGLE-371 > URL: https://issues.apache.org/jira/browse/EAGLE-371 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.5 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Trivial > Fix For: 0.5 > > > eagle-docs will be maintained in > https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't > need maintain duplicated documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371981#comment-15371981 ] ASF GitHub Bot commented on EAGLE-371: -- Github user yonzhang closed the pull request at: https://github.com/apache/incubator-eagle/pull/263 > remove eagle-docs from develop branch > - > > Key: EAGLE-371 > URL: https://issues.apache.org/jira/browse/EAGLE-371 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.5 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Trivial > Fix For: 0.5 > > > eagle-docs will be maintained in > https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't > need maintain duplicated documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371966#comment-15371966 ] ASF GitHub Bot commented on EAGLE-371: -- GitHub user yonzhang opened a pull request: https://github.com/apache/incubator-eagle/pull/263 EAGLE-371 remove eagle-docs from develop branch remove eagle-docs from develop branch Author: Yong Zhang Reviewer: Yong Zhang Closes: #371 You can merge this pull request into a Git repository by running: $ git pull https://github.com/yonzhang/incubator-eagle develop Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/263.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 #263 commit f64496b48dc34ee7b6b57489ac3357b0bfb1465a Author: yonzhang Date: 2016-07-12T00:29:28Z EAGLE-371 remove eagle-docs from develop branch remove eagle-docs from develop branch Author: Yong Zhang Reviewer: Yong Zhang Closes: #371 > remove eagle-docs from develop branch > - > > Key: EAGLE-371 > URL: https://issues.apache.org/jira/browse/EAGLE-371 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.5 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Trivial > Fix For: 0.5 > > > eagle-docs will be maintained in > https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't > need maintain duplicated documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
