edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info
Date Mon, 19 Dec 2016 16:12:58 GMT

    [ https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761569#comment-15761569

ASF GitHub Bot commented on EDGENT-323:

Github user dlaboss commented on a diff in the pull request:

    --- Diff: site/docs/edgent-getting-started.md ---
    @@ -25,7 +25,7 @@ Edgent's primary API is functional where streams are sourced, transformed,
     ### Downloading Apache Edgent
    -To use Edgent, access the source code and build it. You can read more about building
Edgent [here]({{ site.data.project.source_repository_mirror }}/blob/master/DEVELOPMENT.md).
    +To download Edgent, please refer to [here]({{ site.data.project.download }}). And you
can read more about building Edgent [here]({{ site.data.project.source_repository_mirror }}/blob/master/DEVELOPMENT.md).
    --- End diff --
    Suggest migrating the DEVELOPMENT.md references to downloads.html and also clarifying
the getting-started options here.  e.g., replacing the "To use/download Edgent,..." with something
    "To use Edgent you need the Edgent jars.  You can either download the Edgent source and
build it or you can download a pre-built version of Edgent.  See the --downloads page link--.
    Below... "After you build the Edgent package, you ..." change to something like "After
you have the Edgent jars, you ..."

> 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 <website>/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

View raw message