You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Alexander Kachkaev (JIRA)" <ji...@apache.org> on 2016/09/09 13:00:22 UTC

[jira] [Created] (AIRFLOW-497) Release plans & info

Alexander Kachkaev created AIRFLOW-497:
------------------------------------------

             Summary: Release plans & info
                 Key: AIRFLOW-497
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-497
             Project: Apache Airflow
          Issue Type: Wish
          Components: core, docs
            Reporter: Alexander Kachkaev
            Priority: Minor


I did a couple of experiments with airflow several months ago and returned to explore it properly this week. After a few days of quite intensive reading and hacking it still remains unclear to me what's going on with the project ATM.

The latest release is 1.7.1.3, which dates back to 2016-06-13 (three months from now). The docs on pythonhosted sometimes refer to 1.8 and git blame reveals that these mentionings have been there since at least April 2016. JIRA's dashboard has references to versions 1.8 and 2.0, but those only contain lists with issues - no deadline etc.

I imagine that core developers have a clear picture about the situation and it is probably possible to figure things out from the mailing list and gitter, However, it would be good to see roadmap etc. in a slightly more accessible way.

More frequent releases will help a lot as well. I'm seeing some issues when running 1.7.1.3 via docker-airflow / celery, but it's totally unclear whether these still exist on airflow's master branch or even something's wrong with the docker wrapper I'm using. Opening an issue in JIRA seems somewhat stupid in this situation.

Could anyone please increase the clarity of meta?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)