+1 (non-binding)

Tested some example dags with DBT without encountering the issue.

Best,
Wei

> On Sep 13, 2023, at 9:49 PM, Phani Kumar <phani.ku...@astronomer.io.INVALID> 
> wrote:
> 
> +1 non binding
> 
> On Wed, Sep 13, 2023 at 5:03 PM Amogh Desai <amoghdesai....@gmail.com>
> wrote:
> 
>> +1 non binding
>> 
>> Tested with a few dags from my test set. No regression from the last RC.
>> 
>> Thanks,
>> Amogh Desai
>> 
>> On Wed, Sep 13, 2023, 15:19 Pankaj Koti <pankaj.k...@astronomer.io
>> .invalid>
>> wrote:
>> 
>>> +1 (non-binding)
>>> 
>>> Our astronomer-providers (async) DBT DAG based on the provider RC2 ran
>>> fine.
>>> 
>>> Regards,
>>> 
>>> 
>>> 
>>> Pankaj Koti
>>> 
>>> *Senior Software Engineer, *OSS Engineering Team.
>>> Location: Pune, India
>>> 
>>> Timezone: Indian Standard Time (IST)
>>> 
>>> Email: pankaj.k...@astronomer.io
>>> 
>>> Mobile: +91 9730079985
>>> 
>>> 
>>> On Wed, Sep 13, 2023 at 5:01 AM Josh Fell <josh.d.f...@astronomer.io
>>> .invalid>
>>> wrote:
>>> 
>>>> +1 (non-binding)
>>>> 
>>>> Ran a few example DAGs. Everything looks good async and otherwise.
>>>> 
>>>> On Tue, Sep 12, 2023 at 5:37 PM Hussein Awala <huss...@awala.fr>
>> wrote:
>>>> 
>>>>> +1 (binding) - checked my changes and they are present in the RC.
>>>>> 
>>>>> On Tue, Sep 12, 2023 at 11:33 PM Jarek Potiuk <ja...@potiuk.com>
>>> wrote:
>>>>> 
>>>>>> +1 (binding) - checked signatures, checksums, licences, sources
>>>>>> 
>>>>>> On Tue, Sep 12, 2023 at 12:19 PM Elad Kalif <elad...@apache.org>
>>>> wrote:
>>>>>> 
>>>>>>> Hey all,
>>>>>>> 
>>>>>>> I have just cut the *RC2* for dbt.cloud provider. This email is
>>>>> calling a
>>>>>>> vote on the release,
>>>>>>> which will last for 24 hours - which means that it will end on
>>>>> September
>>>>>>> 13, 2023 10:15 AM UTC and until 3 binding +1 votes have been
>>>> received.
>>>>>> Vote
>>>>>>> duration is according to shortened voting period policy as
>> accepted
>>>> in
>>>>>> this
>>>>>>> thread <
>>>>> https://lists.apache.org/thread/cv194w1fqqykrhswhmm54zy9gnnv6kgm
>>>>>>> .
>>>>>>> 
>>>>>>> Consider this my (binding) +1.
>>>>>>> 
>>>>>>> Airflow Providers are available at:
>>>>>>> https://dist.apache.org/repos/dist/dev/airflow/providers/
>>>>>>> 
>>>>>>> *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the binary
>>>>>>> Python "sdist" release - they are also official "sources" for
>> the
>>>>>> provider
>>>>>>> packages.
>>>>>>> 
>>>>>>> *apache_airflow_providers_<PROVIDER>-*.whl are the binary
>>>>>>> Python "wheel" release.
>>>>>>> 
>>>>>>> The test procedure for PMC members is described in
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-pmc-members
>>>>>>> 
>>>>>>> The test procedure for and Contributors who would like to test
>> this
>>>> RC
>>>>> is
>>>>>>> described in:
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-contributors
>>>>>>> 
>>>>>>> 
>>>>>>> Public keys are available at:
>>>>>>> https://dist.apache.org/repos/dist/release/airflow/KEYS
>>>>>>> 
>>>>>>> Please vote accordingly:
>>>>>>> 
>>>>>>> [ ] +1 approve
>>>>>>> [ ] +0 no opinion
>>>>>>> [ ] -1 disapprove with the reason
>>>>>>> 
>>>>>>> 
>>>>>>> Only votes from PMC members are binding, but members of the
>>> community
>>>>> are
>>>>>>> encouraged to test the release and vote with "(non-binding)".
>>>>>>> 
>>>>>>> Please note that the version number excludes the 'rcX' string.
>>>>>>> This will allow us to rename the artifact without modifying
>>>>>>> the artifact checksums when we actually release.
>>>>>>> 
>>>>>>> The status of testing the providers by the community is kept
>> here:
>>>>>>> https://github.com/apache/airflow/issues/34302
>>>>>>> 
>>>>>>> You can find packages as well as detailed changelog following the
>>>> below
>>>>>>> links:
>>>>>>> 
>>>>>>> 
>>>> https://pypi.org/project/apache-airflow-providers-dbt-cloud/3.3.0rc2/
>>>>>>> 
>>>>>>> Cheers,
>>>>>>> Elad Kalif
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 

Reply via email to