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

Raphaël Ouazana commented on JAMES-2569:
----------------------------------------

You are right, I already encountered such issues.

 

As we can assume that users can be using a stable version of the product, we 
should have different link for the different versions. server/3, server/3.1, 
etc.

So I'm not in favor of automaticcally forwarding server/3 to server.

 

But your suggestion of a link indicating there is a new documentation seems 
great.

> Multiple versions of documentation for version 3 are accessible causing 
> confusion.
> ----------------------------------------------------------------------------------
>
>                 Key: JAMES-2569
>                 URL: https://issues.apache.org/jira/browse/JAMES-2569
>             Project: James Server
>          Issue Type: Improvement
>    Affects Versions: 3.0.0, 3.1.0
>            Reporter: Brent Livingston
>            Priority: Minor
>              Labels: documentation
>
> Multiple versions of documentation for Apache James 3+ are visible to the 
> public, which at minimum causes confusion about the project, its 
> functionality, and set up.
> Here is an example. When I did a quick search on Google. This URL was 
> returned: [https://james.apache.org/server/3/release-notes.html]. However, it 
> looks like the latest published version is 
> [https://james.apache.org/server/release-notes.html.]
> GIT reference: 
> [https://github.com/apache/james-project/blob/master/src/site/xdoc/server/release-notes.xml]
> I suggest ../server/3/ URL be automatically forwarded to the latest URL 
> ../server/, OR at minimum at link at top that indicates there is new 
> documentation.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to