I think if anything - that should be a separate page in our GitHub -
which will be a) easier to do b) maybe indeed makes sense c) this is where
we put "developer" docs.
I think we agreed already quite some time ago that "airflow.apache.org" is
generally for the users and all the docs for
Many congratulations Andrey (taragolis :) ) Very very well deserved
Best regards,
*Pankaj Koti*
Senior Software Engineer (Airflow OSS Engineering team)
Location: Pune, Maharashtra, India
Timezone: Indian Standard Time (IST)
Phone: +91 9730079985
On Tue, Jan 16, 2024 at 11:03 PM Mehta,
Hey guys. Just pushed the integration tests for the Qdrant provider with
the CI configurations as requested and some refactoring for the Qdrant hook
to remove redundancy.
On Tue, 16 Jan 2024 at 19:58, Jarek Potiuk wrote:
> > self hosted image and the cloud offering, comprehensive integration
+1 non binding
On Thu, Jan 18, 2024 at 10:30 AM Amogh Desai
wrote:
> +1 non binding
>
> Installed the RC with helm charts, tried a couple of installation
> configurations
> and ran a few examples, not seeing any regression.
>
> Thanks & Regards,
> Amogh Desai
>
> On Thu, Jan 18, 2024 at 12:16
+1 non binding
Installed the RC with helm charts, tried a couple of installation
configurations
and ran a few examples, not seeing any regression.
Thanks & Regards,
Amogh Desai
On Thu, Jan 18, 2024 at 12:16 AM Jed Cunningham
wrote:
> +1 (binding)
>
> Checked signatures, checksums, licences.
Thanks @Jarek Potiuk !
I vaguely knew the process but not in such detail, thanks for putting it
together in this email.
I will visit the document
https://github.com/apache/airflow?tab=readme-ov-file#what-goes-into-the-next-release
and if I find any clarifications, I will send it across as a PR.
+1 (binding)
Checked signatures, checksums, licences. Used it with the helm chart with a
few different configs
Hi Bolke,
Thanks for checking up on this release.
The changes in Airflow.io are mostly improvement changes and this is a
patch release. In patch releases, we don't include improvement changes and
new features. We only include bug fixes, doc changes, and miscellaneous
changes that are not core to
I separate it out, because it seems that despite the efforts to explain and
document how our releases work It's not clear even for the PMC chair, so
likely it warrants a separate thread - also it will be easier to find it in
the archives this way.
I think this is an important topic that all
Just checking:
I see that some improvements to Airflow.io (two weeks ago) were not included
and some provider updates neither. Haven't checked anything else yet.
Is that intentional? Ie. is that the purpose of this release. Other big(ger)
and more recent changes have been included hence
10 matches
Mail list logo
