[
https://issues.apache.org/jira/browse/AIRFLOW-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483757#comment-15483757
]
Alexander Kachkaev commented on AIRFLOW-497:
Thanks for your reply [~artwr],
I saw the roadmap document on wiki and was not sure if this was a good source
of truth because the content was last updated 3 months ago. The most updated
page on the whole wiki seems to be the blog
(https://cwiki.apache.org/confluence/pages/viewrecentblogposts.action?key=AIRFLOW),
which is just full of spam.
My research team is currently looking for a workflow management solution that
we could rely on for at least a couple of years and I imagine that we are not
the only ones here. I understand that Airflow's community is quite young and
there are many things to work on for the core contributors, such as license
cleaning as you mentioned. Keeping your plans and status on the very surface of
what's going on may look not so important, however, lack of overwhelming meta
information is very likely to be a blocker for more people to become engaged
with Airflow and start contributing.
I personally in a bit of doubt about betting on Airflow because of not having a
good picture of it in my head and seeing some not very good looking trends with
issue resolving (the graph on
https://issues.apache.org/jira/browse/AIRFLOW/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
looks more and more red). Many others may be in doubt too (in fact, they might
more sceptical because not everyone has been diligently attempting to watch all
recent Airflow talks and investigating what the transition to Apache might
mean).
What I'd like to ask for is some publicly available "where we are and where we
are going" status update from the developers, ideally once in a week or at
least fortnightly. Release roadmap, important issues, links to discussions,
etc., i.e. some entry-point for those who don't have much time, but are
curious. Despite that this activity wont bring you any instant gain in a form
of a new feature or a bug fix, it will likely engage more people into Airflow
so things will start improving faster.
> 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
> 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 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)
