+1 binding

> On 25 Apr 2025, at 06:23, Amogh Desai <amoghdesai....@gmail.com> wrote:
> 
> +1 non binding
> 
> Tested my changes, works fine:
> #49492 <https://github.com/apache/airflow/pull/49492> doc only change
> #49500 <https://github.com/apache/airflow/pull/49500> is a move from core
> => standard and I checked from downloaded wheel that, well its there:
> 
> (airflow) ➜  apache_airflow_providers_standard-1.1.0rc1.dist-info
> git:(temp-fix-ray) ✗ cat
> airflow/providers/standard/operators/trigger_dagrun.py | grep
> DagIsPaused
> class DagIsPaused(AirflowException):
>    :param fail_when_dag_is_paused: If the dag to trigger is paused,
> DagIsPaused will be raised.
>                    raise DagIsPaused(dag_id=self.trigger_dag_id)
> 
> 
> Ran a general sanity too in standard provider, works as expected.
> 
> 
> Thanks & Regards,
> Amogh Desai
> 
> 
> On Fri, Apr 25, 2025 at 3:22 AM Jens Scheffler <j_scheff...@gmx.de.invalid>
> wrote:
> 
>> Had no time testing but the PMC checks resulted in:
>> 
>> +1 (binding) - Checked SVN, Check in Docker, Reproducible package build,
>> Licenses, Signatures
>> 
>> On 24.04.25 13:17, Elad Kalif wrote:
>>> Hey all,
>>> 
>>> I have just cut the new wave Airflow Providers packages. This email is
>>> calling a vote on the release,
>>> which will last for 72 hours - which means that it will end on April 27,
>>> 2025 11:15 AM UTC and until 3 binding +1 votes have been received.
>>> 
>>> 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
>>> distributions.
>>> 
>>> *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_PROVIDERS.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_PROVIDERS.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/49703
>>> 
>>> The issue is also the easiest way to see important PRs included in the RC
>>> candidates.
>>> Detailed changelog for the providers will be published in the
>> documentation
>>> after the
>>> RC candidates are released.
>>> 
>>> You can find the RC packages in PyPI following these links:
>>> 
>>> 
>> https://pypi.org/project/apache-airflow-providers-common-compat/1.6.1rc1/
>>> https://pypi.org/project/apache-airflow-providers-fab/2.0.2rc1/
>>> https://pypi.org/project/apache-airflow-providers-standard/1.1.0rc1/
>>> 
>>> Cheers,
>>> Elad Kalif
>>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
>> For additional commands, e-mail: dev-h...@airflow.apache.org
>> 
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org

Reply via email to