Hi Airflow Community,

First off, we from Teradata would like to thank you for all your support with 
our provider package. We truly appreciate it!

Since our PR is merged and we’re awaiting the release, I wanted to get some 
clarification on the following topics –

  1.  Is this the 
link<https://airflow.apache.org/docs/apache-airflow/2.8.1/release_notes.html#airflow-2-8-1-2024-01-19>
 we should be following for new Airflow versions? Or, is there anything else we 
should look out for?
  2.  Would Teradata be displayed in the Providers Index after the release?
  3.  Would team Airflow create the PyPI package for Teradata? Or, should we do 
it?


Thanks,
SM

From: K Mallam, Sunil <sunil.kmal...@teradata.com>
Date: Monday, 22 January 2024 at 10:16 PM
To: dev@airflow.apache.org <dev@airflow.apache.org>
Cc: Tworkiewicz, Adam <adam.tworkiew...@teradata.com>, Mishra, Harishankar 
<harishankar.mis...@teradata.com>, Chinthanippu, Satish 
<satish.chinthani...@teradata.com>, Kaxil Naik <kaxiln...@gmail.com>
Subject: [VOTE] [RESULT] New Airflow Community Provider: Teradata
Hi Airflow Community,

We've sent a proposal for Teradata being Airflow's new community provider. 
After 72 hours of voting, we have 9 positive votes (4 binding and 5 
non-binding). Here's a 
link<https://lists.apache.org/thread/l08gf31p89dk8v9md0cdoyqgcglfxwgw> to the 
voting thread.

Please review our PR<https://github.com/apache/airflow/pull/36953> and let us 
know if there's anything else you'd need from us.


Thanks,
Sunil K Mallam
Staff Product Manager – 3rd Party Developer Tools
[A black and orange logo  Description automatically generated]
17095 Via Del Campo Ct.
San Diego, CA 92127
teradata.com<https://www.teradata.com/>
This e-mail is from Teradata Corporation and may contain information that is 
confidential or proprietary. If you are not the intended recipient, do not 
read, copy, or distribute the e-mail or any attachments. Instead, please notify 
the sender and delete the e-mail and any attachments. Thank you.
Please consider the environment before printing.


Reply via email to