[
https://issues.apache.org/jira/browse/AIRFLOW-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970830#comment-15970830
]
ASF subversion and git services commented on AIRFLOW-1000:
----------------------------------------------------------
Commit 4fb05d8cc7a69255c6bff33c7f856eb4a341d5f2 in incubator-airflow's branch
refs/heads/master from [~bolke]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=4fb05d8 ]
[AIRFLOW-1000] Rebrand distribution to Apache Airflow
Per Apache requirements Airflow should be branded
Apache Airflow.
It is impossible to provide a forward compatible
automatic update
path and users will be required to manually
upgrade.
Closes #2172 from bolkedebruin/AIRFLOW-1000
> Rebrand to Apache Airflow instead of Airflow
> --------------------------------------------
>
> Key: AIRFLOW-1000
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1000
> Project: Apache Airflow
> Issue Type: Task
> Affects Versions: 1.8.0
> Reporter: Bolke de Bruin
> Priority: Blocker
> Fix For: 1.8.1
>
>
> Apache requires branding in the form of "Apache Airflow" instead of just
> "Airflow".
> We should figure out a way to rebrand to "Apache Airflow" while having an
> upgrade path as smooth as possible for our users. This could mean that we
> first release side-by-side:
> airflow-1.8.1-apache.incubating
> apache-airflow-1.8.1-incubating
> It seems that pip does support some kind of packaging that helps with this
> (see for example Apache Libcloud).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
