Absolutely! On Sat, May 29, 2021 at 10:50 PM Kaxil Naik <[email protected]> wrote:
> Ok for this release but let's not do that going forward intentionally. > > I would rather not do that, not intentionally atleast i.e. not change/edit > the files that we VOTE on. > > Moving same files between directories is one thing and editing the files > the we vote is another. > > Regards, > Kaxil > > On Sat, May 29, 2021, 21:09 Jarek Potiuk <[email protected]> wrote: > >> We can manually correct filenames in SHASUM while moving. The SHA remains >> the same . >> >> sob., 29 maj 2021, 21:24 użytkownik Kaxil Naik <[email protected]> >> napisał: >> >>> Can we take care of >>> https://github.com/apache/airflow-client-python/pull/22 and re-generate >>> the rc's so once we move them to RELEASE svn repo the SHASUM's are not >>> incorrect >>> >>> On Fri, May 28, 2021 at 9:26 AM Jarek Potiuk <[email protected]> wrote: >>> >>>> ACK. >>>> >>>> On Fri, May 28, 2021 at 10:11 AM Sumit Maheshwari < >>>> [email protected]> wrote: >>>> >>>>> Thanks for validating it Jarek. >>>>> >>>>> About the open issues, like #20 >>>>> <https://github.com/apache/airflow-client-python/issues/20> or #21, >>>>> <https://github.com/apache/airflow-client-python/issues/21> I'm not >>>>> 100% sure but I feel that the issue lies within Airflow's Openapis >>>>> definition manifest itself. So once they get fixed in Airflow, there would >>>>> be a new Airflow release & subsequently there will be a new client >>>>> release, >>>>> which would have a fix for these issues. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Fri, May 28, 2021 at 1:02 PM Jarek Potiuk <[email protected]> wrote: >>>>> >>>>>> +1 (binding) : checked shasums, signatures, licences. Run the API >>>>>> client with example calls against the latest airflow. and the issue #15 >>>>>> is >>>>>> gone. >>>>>> >>>>>> One question: The issue (read only dag_id) : >>>>>> https://github.com/apache/airflow-client-python/issues/21 is still >>>>>> there, but do I understand correctly this is a "known issue" and we are >>>>>> waiting for new version of Open API generator ? >>>>>> >>>>>> J >>>>>> >>>>>> On Thu, May 27, 2021 at 9:25 AM Sumit Maheshwari <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hello everyone, >>>>>>> >>>>>>> I have cut the first release candidate for the Airflow Python Client >>>>>>> 2.1.0. The client consists of APIs corresponding to REST APIs available >>>>>>> in *Apache >>>>>>> Airflow 2.1.0* release. This email is calling a vote on the >>>>>>> release, which will last for 72 hours. Consider this my (binding) +1. >>>>>>> >>>>>>> Airflow Client 2.1.0.rc1 is available at: >>>>>>> >>>>>>> https://dist.apache.org/repos/dist/dev/airflow/clients/python/2.1.0rc1/ >>>>>>> >>>>>>> Or also available at PyPI: >>>>>>> https://pypi.org/project/apache-airflow-client/2.1.0rc1/ >>>>>>> >>>>>>> *airflow-client-2.1.0rc1-source.tar.gz* is a source release that >>>>>>> comes with INSTALL instructions. >>>>>>> *airflow-client-2.1.0rc1-bin.tar.gz* is the binary Python "sdist" >>>>>>> release. >>>>>>> >>>>>>> Public keys are available at: >>>>>>> https://dist.apache.org/repos/dist/release/airflow/KEYS >>>>>>> >>>>>>> Only votes from PMC members are binding, but the release manager >>>>>>> should encourage members of the community to test the release and vote >>>>>>> with >>>>>>> "(non-binding)". >>>>>>> >>>>>>> *Changelog*: >>>>>>> >>>>>>> >>>>>>> *Major changes:*Client code is generated using OpenApi's 5.1.1 >>>>>>> generator CLI >>>>>>> >>>>>>> >>>>>>> *Major fixes:*Fixed the iteration issue on array items caused by >>>>>>> unsupported class 'object' (issue #15) >>>>>>> >>>>>>> >>>>>>> *New API supported:*Permissions >>>>>>> Plugins >>>>>>> Providers >>>>>>> Roles >>>>>>> Users >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> Sumit Maheshwari >>>>>>> PMC Apache Airflow >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> +48 660 796 129 >>>>>> >>>>> >>>> >>>> -- >>>> +48 660 796 129 >>>> >>> -- +48 660 796 129
