[
https://issues.apache.org/jira/browse/LENS-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301148#comment-14301148
]
Hudson commented on LENS-218:
-----------------------------
SUCCESS: Integrated in Lens-Commit #103 (See
[https://builds.apache.org/job/Lens-Commit/103/])
LENS-218 : Add releases menu on site (Sushil Mohanty via amareshwari)
(amareshwari.sr: rev 8902704c99d36096e3e5d9897cc0bf334cf3105f)
* src/site/apt/releases/incompatibility.apt
* src/site/apt/releases/release-note.apt
* src/site/apt/releases/download.apt
* src/site/site.xml
> Add release download links on site
> ----------------------------------
>
> Key: LENS-218
> URL: https://issues.apache.org/jira/browse/LENS-218
> Project: Apache Lens
> Issue Type: Sub-task
> Components: docs
> Reporter: Amareshwari Sriramadasu
> Assignee: Sushil Mohanty
> Fix For: 2.0
>
> Attachments: LENS-218-1.patch, LENS-218-2.patch, LENS-218.patch,
> Screen Shot 2015-01-30 at 9.29.56 PM.png, screenshot-1.png
>
>
> As per - http://www.apache.org/dev/release.html#host-GA
> ---
> Current releases must be served from the ASF mirroring system by placing them
> under http://www.apache.org/dist/. (How to upload releases to the dist/ tree
> is explained below.)
> Project download pages must link to the mirrors and not to the main Apache
> Web site; see instructions for creating download pages for fuller details.
> The website documentation for the software must contain a link to the
> download page for the source.
> Project websites (http://{project}.apache.org), VMs
> (http://{project}.zones.apache.org and http://{project}-vm.apache.org), and
> source control repositories (svn.apache.org and Git repositories) may not be
> used to distribute releases --- that is, releases should not be downloaded
> from them.
> -----
> Instructions for downloading available at
> http://www.apache.org/dev/release-download-pages
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
