Agreed, as long as users can still use different versions through tags, there
are no drawbacks or incompatibilities with this great idea!
Best,
Wei
> On Nov 17, 2023, at 1:39 PM, Aritra Basu wrote:
>
> Agreed, moving to latest by default sounds like a fine idea. I don't see
> any drawbacks to
Agreed, moving to latest by default sounds like a fine idea. I don't see
any drawbacks to it and seems like a good enough time as any to make the
switch with 2.8.0.
--
Regards,
Aritra Basu
On Fri, Nov 17, 2023, 12:33 AM Vincent Beck wrote:
> I agree, by default we should use the latest python v
I am all for it. As we saw already and we see it more in the future -
moving code of out of Airflow core to provider and having separate
provider's release cycle and lifecycle is generally beneficial:
* dependencies can be more decoupled - even if we pin FAB with a particular
version of provider,
+1 for removal
On Thu, Nov 16, 2023 at 1:43 PM Hussein Awala wrote:
> > we would do it branching off at the TAG when the last release happened
> and develop/release a fix from there.
>
> Since it would be possible to release security patches, +1 to remove it.
>
> On Thu 16 Nov 2023 at 21:22, Oli
> we would do it branching off at the TAG when the last release happened
and develop/release a fix from there.
Since it would be possible to release security patches, +1 to remove it.
On Thu 16 Nov 2023 at 21:22, Oliveira, Niko
wrote:
> If no one comes forward willing to support the executor lo
If no one comes forward willing to support the executor long term I'm +1 for
removal.
From: Vincent Beck
Sent: Thursday, November 16, 2023 10:59:40 AM
To: dev@airflow.apache.org
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Suspend (Remove?)
Daskexecutor
I agree, by default we should use the latest python version. Like any package
manager, if the user does not explicitly specify a version, the latest should
be used. If the user wants to use a lower version, he can always pin it.
On 2023/11/16 12:06:17 Jarek Potiuk wrote:
> Hello everyone,
>
> S
+1 for removal
On 2023/11/16 18:54:15 Jarek Potiuk wrote:
> More detailed comparison:
>
> apache-airflow 2.7.* ~ 255.000 downloads/day
> apache-aurflow-provider-dask-executor ~ 900/ day
>
> This means that *apache-airflow-providers-daskexecutor * is downloaded in
> less of *0.3 %* cases, compari
More detailed comparison:
apache-airflow 2.7.* ~ 255.000 downloads/day
apache-aurflow-provider-dask-executor ~ 900/ day
This means that *apache-airflow-providers-daskexecutor * is downloaded in
less of *0.3 %* cases, comparing to *apache-airflow*
I'd say it's negligible usage.
My personal vote
Hello everyone,
Since we are close to the Airflow 2.8.0 release, I would like to propose a
change in the approach for our "default" images.
Currently there are few images that are considered as "default", for
example:
apache/airflow:latest
apache/airflow:2.7.4
Currently (according to our proces
10 matches
Mail list logo
