Hello Everyone,
I have a kind question and request for your opinions about using external
Docker images and downloaded binaries in the official releases for Apache
Airflow.
The question is: How much can we rely on those images being available in
those particular cases:
A) during static checks
B)
Hi Mark & Gavin,
*Per the JDK 15 schedule , we are in Rampdown Phase One* *[1] *
*Please advise if you find any issues while testing the latest Early
Access builds.
*
* Schedule for JDK 15
o *2020/06/11 Rampdown Phase One*
o 2020/07/16 Rampdown Phase Two
o 2020/08/06 Initial
Hey Jarek, thanks for starting this thread. It's a thorny issue, for
sure, especially because binary releases are not "official" from an ASF
perspective.
(Of course, this is a technicality; the fact that your PMC is building
these and linking them from project pages, and/or publishing them out
> Sure. Build tools can even be GPL, and something like a linter isn't a
> hard dependency for Airflow anyway. +1
>
Indeed.
> But we are just about to start releasing Production Image and Helm Chart
> > for Apache Airflow and I started to wonder if this is still acceptable
> > practice when - by
> On Jun 22, 2020, at 6:52 AM, Jarek Potiuk wrote:
> 1) Is this acceptable to have a non-officially released image as a
> dependency in released code for the ASF project?
My understanding the bigger problem is the license of the dependency (and their
dependencies) rather than the official/unof
