[ 
https://issues.apache.org/jira/browse/TAMAYA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827959#comment-16827959
 ] 

ASF subversion and git services commented on TAMAYA-382:
--------------------------------------------------------

Commit 5591ceecefb0e1fe1c0c2134d0f44714f6a9f01e in incubator-tamaya-site's 
branch refs/heads/master from William Lieurance
[ https://gitbox.apache.org/repos/asf?p=incubator-tamaya-site.git;h=5591cee ]

TAMAYA-382 link updates

This PR makes 2 changes, per the February 2019 report.

1.  Updates artifact download links to use the mirror lookup link or
archive link as makes sense.
2.  Updates mail-archive link to work around problems putting the '@'
symbol in links in Asciidoc, but with the Apache list server not
accepting any encoded values in the URL.

I also changed a reference from apache gitbox over to github for new
devs, which seems in line with the move we made last year.


> Adapt download secton of webpage
> --------------------------------
>
>                 Key: TAMAYA-382
>                 URL: https://issues.apache.org/jira/browse/TAMAYA-382
>             Project: Tamaya
>          Issue Type: Bug
>          Components: Website
>            Reporter: Philipp Ottlinger
>            Assignee: William Lieurance
>            Priority: Major
>             Fix For: 0.4-incubating
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> As noted during report phase Feb2019:
> {code:java}
> (1) The download page and archives need to follow release distribution policy 
> at https://www.apache.org/dev/release-distribution.html#download-links
> (a) The current release needs to point to the mirrors. Follow the link from 
> the policy or take a look at httpd.apache.org.
> (b) Old releases need to be removed from the main dist area and instead you 
> need to reference the archives,
> (2) The links to the mailing lists look like the anchor is missing or 
> incorrect.{code}
> Regenerate website after fixes are applied.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to