[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info
[ https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15769164#comment-15769164 ] ASF GitHub Bot commented on EDGENT-323: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent-website/pull/83 > edgent.apache.org needs refactoring for "downloads" info > > > Key: EDGENT-323 > URL: https://issues.apache.org/jira/browse/EDGENT-323 > Project: Edgent > Issue Type: Bug >Reporter: Dale LaBossiere >Assignee: Cazen Lee > > A precursor to making a release announcement is that the project's website is > updated for the release. > There are several places in the current edgent.apache.org dealing with > downloads. Downloads are a bit more complicated in the ASF world -- with the > official www.apache.org/dist site (and mirrors, and dynamic resolver) for > releases (with src and convenience binary bundles) as well as the Edgent ASF > git repo and mirror at github. > We need a edgent.apache.org/downloads.html page that all other references / > buttons point to. That page can clarify these different locations and their > uses, provide a list of releases, and release specific links (dynamic-mirror > links for bundles, backup-mirror links for the md5/sha/asc files, > release-specific-github link). > Fwiw, it seems common for ASF release announcements to refer people to > /downloads.html as opposed just to the project's main page. > Various locations related to downloads in edgent.apache.org: > - Download Source button - links to github > - Community tab -> Source Code - links to github > - Getting Started tab -> Download Source - links to github > - docs/community - "Source code" - no mention of ASF release, ... > - docs/faq > - "Where can I download..." github and quarks-edge - see EDGENT-312 / > https://github.com/apache/incubator-edgent-website/pull/80 > - "Where can I get the code?" - links to github > - docs/edgent-getting-started > - upper left says Edgent Version 0.3.0 > - "Downloading Apache Edgent" - has link to DEVELOPMENT.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info
[ https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15769162#comment-15769162 ] ASF GitHub Bot commented on EDGENT-323: --- GitHub user Cazen opened a pull request: https://github.com/apache/incubator-edgent-website/pull/83 [EDGENT-323] change some links setting You can merge this pull request into a Git repository by running: $ git pull https://github.com/Cazen/incubator-edgent-website EDGENT-323 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-edgent-website/pull/83.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 #83 commit 94572384a4dda3794d7dcad37cd5670dc334d033 Author: Cazen LeeDate: 2016-12-22T05:57:54Z change some links setting > edgent.apache.org needs refactoring for "downloads" info > > > Key: EDGENT-323 > URL: https://issues.apache.org/jira/browse/EDGENT-323 > Project: Edgent > Issue Type: Bug >Reporter: Dale LaBossiere >Assignee: Cazen Lee > > A precursor to making a release announcement is that the project's website is > updated for the release. > There are several places in the current edgent.apache.org dealing with > downloads. Downloads are a bit more complicated in the ASF world -- with the > official www.apache.org/dist site (and mirrors, and dynamic resolver) for > releases (with src and convenience binary bundles) as well as the Edgent ASF > git repo and mirror at github. > We need a edgent.apache.org/downloads.html page that all other references / > buttons point to. That page can clarify these different locations and their > uses, provide a list of releases, and release specific links (dynamic-mirror > links for bundles, backup-mirror links for the md5/sha/asc files, > release-specific-github link). > Fwiw, it seems common for ASF release announcements to refer people to > /downloads.html as opposed just to the project's main page. > Various locations related to downloads in edgent.apache.org: > - Download Source button - links to github > - Community tab -> Source Code - links to github > - Getting Started tab -> Download Source - links to github > - docs/community - "Source code" - no mention of ASF release, ... > - docs/faq > - "Where can I download..." github and quarks-edge - see EDGENT-312 / > https://github.com/apache/incubator-edgent-website/pull/80 > - "Where can I get the code?" - links to github > - docs/edgent-getting-started > - upper left says Edgent Version 0.3.0 > - "Downloading Apache Edgent" - has link to DEVELOPMENT.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info
[ https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15769122#comment-15769122 ] ASF GitHub Bot commented on EDGENT-323: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent-website/pull/82 > edgent.apache.org needs refactoring for "downloads" info > > > Key: EDGENT-323 > URL: https://issues.apache.org/jira/browse/EDGENT-323 > Project: Edgent > Issue Type: Bug >Reporter: Dale LaBossiere >Assignee: Cazen Lee > > A precursor to making a release announcement is that the project's website is > updated for the release. > There are several places in the current edgent.apache.org dealing with > downloads. Downloads are a bit more complicated in the ASF world -- with the > official www.apache.org/dist site (and mirrors, and dynamic resolver) for > releases (with src and convenience binary bundles) as well as the Edgent ASF > git repo and mirror at github. > We need a edgent.apache.org/downloads.html page that all other references / > buttons point to. That page can clarify these different locations and their > uses, provide a list of releases, and release specific links (dynamic-mirror > links for bundles, backup-mirror links for the md5/sha/asc files, > release-specific-github link). > Fwiw, it seems common for ASF release announcements to refer people to > /downloads.html as opposed just to the project's main page. > Various locations related to downloads in edgent.apache.org: > - Download Source button - links to github > - Community tab -> Source Code - links to github > - Getting Started tab -> Download Source - links to github > - docs/community - "Source code" - no mention of ASF release, ... > - docs/faq > - "Where can I download..." github and quarks-edge - see EDGENT-312 / > https://github.com/apache/incubator-edgent-website/pull/80 > - "Where can I get the code?" - links to github > - docs/edgent-getting-started > - upper left says Edgent Version 0.3.0 > - "Downloading Apache Edgent" - has link to DEVELOPMENT.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info
[ https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15767554#comment-15767554 ] ASF GitHub Bot commented on EDGENT-323: --- Github user dlaboss commented on the issue: https://github.com/apache/incubator-edgent-website/pull/82 +1 thanks! > edgent.apache.org needs refactoring for "downloads" info > > > Key: EDGENT-323 > URL: https://issues.apache.org/jira/browse/EDGENT-323 > Project: Edgent > Issue Type: Bug >Reporter: Dale LaBossiere >Assignee: Cazen Lee > > A precursor to making a release announcement is that the project's website is > updated for the release. > There are several places in the current edgent.apache.org dealing with > downloads. Downloads are a bit more complicated in the ASF world -- with the > official www.apache.org/dist site (and mirrors, and dynamic resolver) for > releases (with src and convenience binary bundles) as well as the Edgent ASF > git repo and mirror at github. > We need a edgent.apache.org/downloads.html page that all other references / > buttons point to. That page can clarify these different locations and their > uses, provide a list of releases, and release specific links (dynamic-mirror > links for bundles, backup-mirror links for the md5/sha/asc files, > release-specific-github link). > Fwiw, it seems common for ASF release announcements to refer people to > /downloads.html as opposed just to the project's main page. > Various locations related to downloads in edgent.apache.org: > - Download Source button - links to github > - Community tab -> Source Code - links to github > - Getting Started tab -> Download Source - links to github > - docs/community - "Source code" - no mention of ASF release, ... > - docs/faq > - "Where can I download..." github and quarks-edge - see EDGENT-312 / > https://github.com/apache/incubator-edgent-website/pull/80 > - "Where can I get the code?" - links to github > - docs/edgent-getting-started > - upper left says Edgent Version 0.3.0 > - "Downloading Apache Edgent" - has link to DEVELOPMENT.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info
[ https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765636#comment-15765636 ] ASF GitHub Bot commented on EDGENT-323: --- Github user justinmclean commented on a diff in the pull request: https://github.com/apache/incubator-edgent-website/pull/82#discussion_r93351844 --- Diff: site/docs/downloads.md --- @@ -0,0 +1,13 @@ +--- +title: Downloads +--- + --- End diff -- you might also want to add a link to the KEYS and asc files so the releases can be verified. > edgent.apache.org needs refactoring for "downloads" info > > > Key: EDGENT-323 > URL: https://issues.apache.org/jira/browse/EDGENT-323 > Project: Edgent > Issue Type: Bug >Reporter: Dale LaBossiere >Assignee: Cazen Lee > > A precursor to making a release announcement is that the project's website is > updated for the release. > There are several places in the current edgent.apache.org dealing with > downloads. Downloads are a bit more complicated in the ASF world -- with the > official www.apache.org/dist site (and mirrors, and dynamic resolver) for > releases (with src and convenience binary bundles) as well as the Edgent ASF > git repo and mirror at github. > We need a edgent.apache.org/downloads.html page that all other references / > buttons point to. That page can clarify these different locations and their > uses, provide a list of releases, and release specific links (dynamic-mirror > links for bundles, backup-mirror links for the md5/sha/asc files, > release-specific-github link). > Fwiw, it seems common for ASF release announcements to refer people to > /downloads.html as opposed just to the project's main page. > Various locations related to downloads in edgent.apache.org: > - Download Source button - links to github > - Community tab -> Source Code - links to github > - Getting Started tab -> Download Source - links to github > - docs/community - "Source code" - no mention of ASF release, ... > - docs/faq > - "Where can I download..." github and quarks-edge - see EDGENT-312 / > https://github.com/apache/incubator-edgent-website/pull/80 > - "Where can I get the code?" - links to github > - docs/edgent-getting-started > - upper left says Edgent Version 0.3.0 > - "Downloading Apache Edgent" - has link to DEVELOPMENT.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info
[ https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765625#comment-15765625 ] ASF GitHub Bot commented on EDGENT-323: --- Github user Cazen commented on the issue: https://github.com/apache/incubator-edgent-website/pull/82 @dlaboss Thank you for detailed guide. I will reflect your requirements soon > edgent.apache.org needs refactoring for "downloads" info > > > Key: EDGENT-323 > URL: https://issues.apache.org/jira/browse/EDGENT-323 > Project: Edgent > Issue Type: Bug >Reporter: Dale LaBossiere >Assignee: Cazen Lee > > A precursor to making a release announcement is that the project's website is > updated for the release. > There are several places in the current edgent.apache.org dealing with > downloads. Downloads are a bit more complicated in the ASF world -- with the > official www.apache.org/dist site (and mirrors, and dynamic resolver) for > releases (with src and convenience binary bundles) as well as the Edgent ASF > git repo and mirror at github. > We need a edgent.apache.org/downloads.html page that all other references / > buttons point to. That page can clarify these different locations and their > uses, provide a list of releases, and release specific links (dynamic-mirror > links for bundles, backup-mirror links for the md5/sha/asc files, > release-specific-github link). > Fwiw, it seems common for ASF release announcements to refer people to > /downloads.html as opposed just to the project's main page. > Various locations related to downloads in edgent.apache.org: > - Download Source button - links to github > - Community tab -> Source Code - links to github > - Getting Started tab -> Download Source - links to github > - docs/community - "Source code" - no mention of ASF release, ... > - docs/faq > - "Where can I download..." github and quarks-edge - see EDGENT-312 / > https://github.com/apache/incubator-edgent-website/pull/80 > - "Where can I get the code?" - links to github > - docs/edgent-getting-started > - upper left says Edgent Version 0.3.0 > - "Downloading Apache Edgent" - has link to DEVELOPMENT.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info
[ https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15761517#comment-15761517 ] ASF GitHub Bot commented on EDGENT-323: --- Github user dlaboss commented on a diff in the pull request: https://github.com/apache/incubator-edgent-website/pull/82#discussion_r93057962 --- Diff: site/docs/faq.md --- @@ -44,7 +44,7 @@ Edgent is a tool for edge analytics that allows you to be more productive. Edgen ## Where can I download Apache Edgent to try it out? -You can download the source from Apache and build it yourself [here]({{ site.data.project.source_repository_mirror }}). You can also find already pre-built Apache releases of Edgent for download [here]({{ site.data.project.apache_release_location }}) (But this location is temporarily unavailable until we get the first release out). +You can download the source from Apache and build it yourself [here]({{ site.data.project.download }}). You can also find already pre-built Apache releases of Edgent for download [here]({{ site.data.project.apache_release_location }}) (But this location is temporarily unavailable until we get the first release out). --- End diff -- I suggest simplifying this and adding all of the details to the downloads page. E.g., simply say "You can download Apache Edgent from --link to the downloads.html page--. > edgent.apache.org needs refactoring for "downloads" info > > > Key: EDGENT-323 > URL: https://issues.apache.org/jira/browse/EDGENT-323 > Project: Edgent > Issue Type: Bug >Reporter: Dale LaBossiere >Assignee: Cazen Lee > > A precursor to making a release announcement is that the project's website is > updated for the release. > There are several places in the current edgent.apache.org dealing with > downloads. Downloads are a bit more complicated in the ASF world -- with the > official www.apache.org/dist site (and mirrors, and dynamic resolver) for > releases (with src and convenience binary bundles) as well as the Edgent ASF > git repo and mirror at github. > We need a edgent.apache.org/downloads.html page that all other references / > buttons point to. That page can clarify these different locations and their > uses, provide a list of releases, and release specific links (dynamic-mirror > links for bundles, backup-mirror links for the md5/sha/asc files, > release-specific-github link). > Fwiw, it seems common for ASF release announcements to refer people to > /downloads.html as opposed just to the project's main page. > Various locations related to downloads in edgent.apache.org: > - Download Source button - links to github > - Community tab -> Source Code - links to github > - Getting Started tab -> Download Source - links to github > - docs/community - "Source code" - no mention of ASF release, ... > - docs/faq > - "Where can I download..." github and quarks-edge - see EDGENT-312 / > https://github.com/apache/incubator-edgent-website/pull/80 > - "Where can I get the code?" - links to github > - docs/edgent-getting-started > - upper left says Edgent Version 0.3.0 > - "Downloading Apache Edgent" - has link to DEVELOPMENT.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info
[ https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15761473#comment-15761473 ] ASF GitHub Bot commented on EDGENT-323: --- Github user dlaboss commented on the issue: https://github.com/apache/incubator-edgent-website/pull/82 [~Cazen] thanks for picking up this jira! (and your other deliveries the last couple of days) I sent a clarifying note to @dev regarding the location of the release artifacts. Hope that clears some things up: https://www.mail-archive.com/dev@edgent.apache.org/msg00933.html. Yes, a cool page is highly desired I think. If that can be achieved in a day or two that would be great. Otherwise a quick/simple first-iteration page will allow making the release announcement sooner and the page can be enhanced after the fact. > edgent.apache.org needs refactoring for "downloads" info > > > Key: EDGENT-323 > URL: https://issues.apache.org/jira/browse/EDGENT-323 > Project: Edgent > Issue Type: Bug >Reporter: Dale LaBossiere >Assignee: Cazen Lee > > A precursor to making a release announcement is that the project's website is > updated for the release. > There are several places in the current edgent.apache.org dealing with > downloads. Downloads are a bit more complicated in the ASF world -- with the > official www.apache.org/dist site (and mirrors, and dynamic resolver) for > releases (with src and convenience binary bundles) as well as the Edgent ASF > git repo and mirror at github. > We need a edgent.apache.org/downloads.html page that all other references / > buttons point to. That page can clarify these different locations and their > uses, provide a list of releases, and release specific links (dynamic-mirror > links for bundles, backup-mirror links for the md5/sha/asc files, > release-specific-github link). > Fwiw, it seems common for ASF release announcements to refer people to > /downloads.html as opposed just to the project's main page. > Various locations related to downloads in edgent.apache.org: > - Download Source button - links to github > - Community tab -> Source Code - links to github > - Getting Started tab -> Download Source - links to github > - docs/community - "Source code" - no mention of ASF release, ... > - docs/faq > - "Where can I download..." github and quarks-edge - see EDGENT-312 / > https://github.com/apache/incubator-edgent-website/pull/80 > - "Where can I get the code?" - links to github > - docs/edgent-getting-started > - upper left says Edgent Version 0.3.0 > - "Downloading Apache Edgent" - has link to DEVELOPMENT.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info
[ https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15758915#comment-15758915 ] ASF GitHub Bot commented on EDGENT-323: --- Github user Cazen commented on the issue: https://github.com/apache/incubator-edgent-website/pull/82 - I noticed that we need publish our artifacts to dist.apache.org. So download links will be changed after publishing. - And I'm afraid that do we need a cool download page that includes design rather than a simple download page under doc(doc/download.html)? > edgent.apache.org needs refactoring for "downloads" info > > > Key: EDGENT-323 > URL: https://issues.apache.org/jira/browse/EDGENT-323 > Project: Edgent > Issue Type: Bug >Reporter: Dale LaBossiere >Assignee: Cazen Lee > > A precursor to making a release announcement is that the project's website is > updated for the release. > There are several places in the current edgent.apache.org dealing with > downloads. Downloads are a bit more complicated in the ASF world -- with the > official www.apache.org/dist site (and mirrors, and dynamic resolver) for > releases (with src and convenience binary bundles) as well as the Edgent ASF > git repo and mirror at github. > We need a edgent.apache.org/downloads.html page that all other references / > buttons point to. That page can clarify these different locations and their > uses, provide a list of releases, and release specific links (dynamic-mirror > links for bundles, backup-mirror links for the md5/sha/asc files, > release-specific-github link). > Fwiw, it seems common for ASF release announcements to refer people to > /downloads.html as opposed just to the project's main page. > Various locations related to downloads in edgent.apache.org: > - Download Source button - links to github > - Community tab -> Source Code - links to github > - Getting Started tab -> Download Source - links to github > - docs/community - "Source code" - no mention of ASF release, ... > - docs/faq > - "Where can I download..." github and quarks-edge - see EDGENT-312 / > https://github.com/apache/incubator-edgent-website/pull/80 > - "Where can I get the code?" - links to github > - docs/edgent-getting-started > - upper left says Edgent Version 0.3.0 > - "Downloading Apache Edgent" - has link to DEVELOPMENT.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)