airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-52) Release airflow 1.7.1
Date Thu, 05 May 2016 20:38:12 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273026#comment-15273026
] 

Jakob Homan commented on AIRFLOW-52:
------------------------------------

So, the release will be coordinated (and built from) github and github resources? I think
Chris is right, but I'd be concerned about running the vote or whatever process was being
used for the release on ASF resources.  I'd want to avoid the appearance of trying to make
an end-run around asf procedure (which I know isn't the case).

I'm honestly not sure though; may be worth pinging general@incubator.

> Release airflow 1.7.1
> ---------------------
>
>                 Key: AIRFLOW-52
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-52
>             Project: Apache Airflow
>          Issue Type: Task
>          Components: ease
>            Reporter: Dan Davydov
>            Assignee: Dan Davydov
>              Labels: release
>
> Release the airflow 1.7.1 tag.
> Current status:
> I found the commit that caused the slowdown in 1.7.1rc3 yesterday (some DAGs were timing
out when they got parsed via collect_dags).
> Working with the owner of the commit to decide whether it's better to roll forward with
a fix or revert the commit for now.
> The way to catch these issues in the future is an integration test that asserts a given
non-trivial DAG parses under X seconds.



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

Mime
View raw message