You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2017/04/17 16:09:41 UTC

[jira] [Closed] (AIRFLOW-1000) Rebrand to Apache Airflow instead of Airflow

     [ https://issues.apache.org/jira/browse/AIRFLOW-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Riccomini closed AIRFLOW-1000.
------------------------------------
    Resolution: Fixed
      Assignee: Bolke de Bruin

> 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
>            Assignee: 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)