airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ash Berlin-Taylor <...@apache.org>
Subject Re: Airflow RC releases on pypi
Date Mon, 29 Apr 2019 10:53:17 GMT
Hi Ahmet,

Our view was so long as we don't call them "releases" this is okay as anything we publish
on PyPi isn't an official Apache release anyway (those can only happen from https://www.apache.org/dist/)
- and given that a beta/RC published to PyPi has to be explicitly installed by an end user
this fits in with the RC section on http://www.apache.org/legal/release-policy.html#release-types

Here's a link to one of our RC Vote emails for our wording https://lists.apache.org/thread.html/304f64f0724b7708dc3a80430b1b1f63e802ee70e87d8872f402860b@%3Cdev.airflow.apache.org%3E

HTH,
Ash

> On 26 Apr 2019, at 23:43, Ahmet Altay <altay@google.com.INVALID> wrote:
> 
> Hi all,
> 
> I work on Apache Beam. We have an ongoing discussion about publishing
> beam's RC candidates on pypi [1]. I noticed that Airflow is already doing
> this [2] (e.g. 1.10.3rc2 etc.). In Beam's discussion a question come about
> whether publishing RC artifacts are compatible with Apache release policy
> [3].
> 
> I would like to hear from Airflow community about, have you had a
> discussion about this? What are your thoughts on benefits and issues with
> publishing rc releases on pypi.
> 
> Looking forward to learning from you.
> 
> Thank you!
> Ahmet
> 
> [1]
> https://lists.apache.org/thread.html/f071f8ab9f115636b9e6a6cabcfccbe2bb980d4394fe5581c59a4db6@%3Cdev.beam.apache.org%3E
> [2] https://pypi.org/project/apache-airflow/#history
> [3] http://www.apache.org/legal/release-policy.html


Mime
View raw message