airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arthur Wiedmer (JIRA)" <>
Subject [jira] [Commented] (AIRFLOW-497) Release plans & info
Date Fri, 09 Sep 2016 20:38:20 GMT


Arthur Wiedmer commented on AIRFLOW-497:

Hi Alexander,

I think I can leave a quick update here. While the committers and various contributors have
worked on several improvements, we have been blocked on navigating our first apache release
(a decent amount of contributors are new to this process and it takes a little getting used

The main issues that the next release will address are licensing issues, stripping out components
that were not compatible with the Apache License as well as a few bug fixes. We hope to be
able to release more often in the future once we document the release process internally and
make sure we are starting with the right base to be a successful project under the Apache

A general idea of the improvement roadmap can be found on the wiki :

Feel free to ping the dev mailing list also if you have more questions or want to start a
conversation about releases.


> Release plans & info
> --------------------
>                 Key: AIRFLOW-497
>                 URL:
>             Project: Apache Airflow
>          Issue Type: Wish
>          Components: core, docs
>            Reporter: Alexander Kachkaev
>            Priority: Minor
>              Labels: build, newbie, release
> 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, 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
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

View raw message