[
https://issues.apache.org/jira/browse/KNOX-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775070#comment-16775070
]
Sandor Molnar commented on KNOX-1561:
-------------------------------------
[~krisden]
Currently, we have _N_ release pages under {{Pages /}} {{Index}} in Confluence.
Instead, we may have only one page with the following sections:
* Downloads: contains a table with the following columns
** Version
** Release date (is it safe to assume that the {{Created date}} field of
different release pages indicates the release date?)
** Source archive
** Gateway server binary archive
** Gateway client binary archive (populated only where available)
** User guide
** Developer guide
** Quick start guide? (I'm not sure if this is needed)
* Keys : contains a link to keys (common for all releases)
* Export control (common for all releases)
* Release integrity verification: providing a generic description (version
X.Y) with a sample (i.e. version 1.2.0)
* Footer: TM, License, Policy
If all done and reviewed we may archive the previously created _N_ release
pages.
There is on release where there are sub-pages: we may keep those and add a link
in our downloads table; however, I'm not sure if we really need to do this...
What do you think?
> Create downloads page with table
> --------------------------------
>
> Key: KNOX-1561
> URL: https://issues.apache.org/jira/browse/KNOX-1561
> Project: Apache Knox
> Issue Type: Improvement
> Components: Release, Site
> Reporter: Kevin Risden
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 1.3.0
>
>
> KNOX-1405 identified that it would be easier to update a single downloads
> page instead of multiple individual pages. We should do something like that :)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
