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

ASF subversion and git services commented on AIRFLOW-3656:
----------------------------------------------------------

Commit 7ce959774c7a431d086d74b24a6f47753ab7c90e in airflow's branch 
refs/heads/v1-10-test from Kaxil Naik
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=7ce9597 ]

[AIRFLOW-3656] Show doc link for the current installed version (#6690)

(cherry-picked from commit 15e30dd10a8c5c479a1ff90c74d0ca6d75d1baa1)


> Airflow Web UI link to the docs should be dynamic to Airflow version
> --------------------------------------------------------------------
>
>                 Key: AIRFLOW-3656
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3656
>             Project: Apache Airflow
>          Issue Type: Task
>          Components: ui
>    Affects Versions: 1.10.1
>            Reporter: jack
>            Assignee: Kaxil Naik
>            Priority: Major
>             Fix For: 1.10.7
>
>         Attachments: 0101.PNG
>
>
> Currently in the UI Docs->Documentation directs to 
> [https://airflow.incubator.apache.org/]
>  # This should be changed to [https://airflow.readthedocs.io/en/stable/]  
> because in readthedocs the user can actually select the docs version. while 
> the current one refers only to Master branch and the user can't change it nor 
> would even know it.
>  # Preferably by clicking on the Docs->Documentation it will pick up the 
> Airflow version and point directly to the user Airflow version. Meaning that 
> if the user runs Airflow 1.10.0 it will point to 
> [https://airflow.readthedocs.io/en/1.10.0/]  The airflow version is already 
> transparent in the UI (About->Version) so it shouldn't be difficult to build 
> this link.
>  
> Previous PR that was related to the doc link is (by [~kaxilnaik]):
> https://github.com/apache/airflow/pull/3050



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to