wooohooo!
On Mon, Nov 6, 2023 at 7:58 AM Ephraim Anierobi
wrote:
> Dear Airflow community,
>
> I'm happy to announce that Airflow 2.7.3 was just released.
>
> The released sources and packages can be downloaded via
>
Dear Airflow community,
I'm happy to announce that Airflow 2.7.3 was just released.
The released sources and packages can be downloaded via
https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-sources.html
Other installation methods are described in
Hello,
Apache Airflow 2.7.3(based on RC1) has been accepted.
4 "+1" binding votes received:
- Ephraim Anierobi
- Pierre Jeambrun
- Jarek Potiuk
- Hussein Awala
4 "+1" non-binding votes received:
- Pankaj Singh
- Rahul Vats
- Aritra Basu
- Wei Lee
Vote thread:
+1 (non-binding)
Best,
Wei
> On Nov 6, 2023, at 12:17 PM, Aritra Basu wrote:
>
> +1 (non-binding)
>
> --
> Regards,
> Aritra Basu
>
> On Mon, Nov 6, 2023, 9:30 AM Rahul Vats wrote:
>
>> +1 (non-binding)
>>
>> Regards,
>> Rahul Vats
>> 9953794332
>>
>>
>> On Sun, 5 Nov 2023 at 10:53,
+1 (non-binding)
--
Regards,
Aritra Basu
On Mon, Nov 6, 2023, 9:30 AM Rahul Vats wrote:
> +1 (non-binding)
>
> Regards,
> Rahul Vats
> 9953794332
>
>
> On Sun, 5 Nov 2023 at 10:53, Pankaj Singh
> wrote:
>
> > +1 (non-binding)
> >
> > my changes look good to me.
> >
> > On Sat, Nov 4, 2023 at
+1 (non-binding)
Regards,
Rahul Vats
9953794332
On Sun, 5 Nov 2023 at 10:53, Pankaj Singh wrote:
> +1 (non-binding)
>
> my changes look good to me.
>
> On Sat, Nov 4, 2023 at 10:11 PM Hussein Awala wrote:
>
> > +1 (binding) I checked the checksums, the signatures, the licences, the
> >
Hey fellow Airflowers,
As discussed in
https://lists.apache.org/thread/c1n6gqrx3v00z1qr1nr10obvvn2v1rcz, I am
calling for a lazy consensus to decouple the API clients versioning from
core.
This is needed to be able to move forward with the clients and modernise
our clients release process.
Ok, seems like we are agreeing, I will follow up with a lazy consensus.
Le jeu. 2 nov. 2023 à 14:43, Jarek Potiuk a écrit :
> Yeah. I thought a bit more about it and yeah, with next gen and the
> versioning still aligned with airflow l we are likely to fall in the same
> trap. And will have to
TL;DR; Yes, if you use our reference docker images, you are already
following the "How to reproducibly install Airflow" recommendation, because
this is what we do when preparing the release, also because those images
are generally "frozen" in time once released.
*Little longer explanation if you
Dear Jarek,
Thank you for this really useful recommandation!
But, just, I would like to be sure of something: when you say that 'pip'
is the only way to install Airflow in a reproducible way, you mean
comparing to installation from sources?
I guess the installation from Docker images is
10 matches
Mail list logo