Thanks for the confirmation Jarek. I would create a new Voting thread, hence closing this one.
On Wed, Apr 14, 2021 at 1:21 PM Jarek Potiuk <[email protected]> wrote: > correct > > On Wed, Apr 14, 2021 at 6:05 AM Sumit Maheshwari <[email protected]> > wrote: > >> Thanks, Jarek and Kaxil for catching this before it went live. >> >> So if I understand correctly, the package name would be >> *apache-airflow-client*, which means users would be able to install it >> via *pip install apache-airflow-client*. However, while using the client >> in their python code, they would be able to simply call *import >> airflow-client* and not apache-airflow-client, correct? >> >> >> >> On Wed, Apr 14, 2021 at 1:30 AM Kaxil Naik <[email protected]> wrote: >> >>> Oh yes it should be called apache-airflow-client. >>> >>> For docker and helm chart it is different since we have the "apache" >>> name in org or add helm repo. >>> >>> But for this case, we should just for consistency too as the artifact >>> published on PyPI and installable / searched via pip too is apache-airflow >>> :) >>> >>> Regards, >>> Kaxil >>> >>> On Tue, Apr 13, 2021, 20:31 Jarek Potiuk <[email protected]> wrote: >>> >>>> To clarify - Use 'apache' as the prefix of the name of the package) => >>>> 'apache-airflow-client' >>>> >>>> J, >>>> >>>> >>>> On Tue, Apr 13, 2021 at 9:29 PM Jarek Potiuk <[email protected]> wrote: >>>> >>>>> It looks really good now - flawless installation, check and very well >>>>> documented :). Thanks for being receptive Sumit :) >>>>> >>>>> But I have noticed one thing (I noticed it after I started to follow >>>>> the documentation so sorry for not pointing it before). >>>>> >>>>> The name of the package also in PyPI is "airflow-client". But all >>>>> other packages of ours start with "apache-airflow". >>>>> >>>>> I think (Ash , Kaxil?) we are obliged to use 'apache' as the name of >>>>> the package. >>>>> >>>>> I think that calls for -1 if I am right about it. >>>>> >>>>> I >>>>> >>>>> On Mon, Apr 12, 2021 at 5:42 PM Sumit Maheshwari < >>>>> [email protected]> wrote: >>>>> >>>>>> Hello everyone, >>>>>> >>>>>> I have cut the second release candidate for the Airflow Python Client >>>>>> 2.0.0rc2. The client consists of APIs corresponding to REST APIs >>>>>> available >>>>>> in *Apache Airflow 2.0.1* release. This email is calling a vote on >>>>>> the release, which will last for 72 hours. Consider this my (binding) +1. >>>>>> >>>>>> Airflow Client 2.0.0.rc2 is available at: >>>>>> >>>>>> https://dist.apache.org/repos/dist/dev/airflow/clients/python/2.0.0rc2/ >>>>>> >>>>>> *airflow-client-2.0.0rc2-source.tar.gz* is a source release that >>>>>> comes with INSTALL instructions. >>>>>> *airflow-client-2.0.0rc2-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)". >>>>>> >>>>>> As this is the first release, there is no changelog. The source code >>>>>> for this release can be found here: >>>>>> https://github.com/apache/airflow-client-python/tree/r2.0 >>>>>> >>>>>> Thanks, >>>>>> Sumit Maheshwari >>>>>> PMC Apache Airflow >>>>>> >>>>> >>>>> >>>>> -- >>>>> +48 660 796 129 >>>>> >>>> >>>> >>>> -- >>>> +48 660 796 129 >>>> >>> > > -- > +48 660 796 129 >
