1.10.0 isn't officially released yet, so that's why it's not on PyPi/tagged yet. (As we are still in the Incubation phase of the project we need our mentors to also sign off on our RC after we, the Airflow community, have voted on it)
But yes, we should push the tags to Github. I've done that: git tag 1.10.0rc3 862ad8b9 # [AIRFLOW-XXX] Update changelog for 1.10 git tag 1.10.0rc4 26e0d449 # AIRFLOW-XXX] Update changelog for 1.10 git push --tags github Having just updated the instructions (https://cwiki.apache.org/confluence/display/AIRFLOW/Releasing+Airflow <https://cwiki.apache.org/confluence/display/AIRFLOW/Releasing+Airflow>) I suspect the tags were in Bolke's local checkout. I hope I got the commits right -ash > On 15 Aug 2018, at 17:34, James Meickle <[email protected]> > wrote: > > Can we make it a policy going forward to push GH tags for all RCs as part > of the release announcement? I deploy via the incubator-airflow repo, but > currently it only has tags for up to RC2, which means I have to look up and > then specify an ugly-looking commit to deploy an RC :( > > On Wed, Aug 15, 2018 at 10:54 AM Taylor Edmiston <[email protected]> > wrote: > >> Krish - You can also use the RCs before they're released on PyPI if you'd >> like to help test. Instead of: >> >> pip install apache-airflow >> >> You can install the 1.10 stable latest with: >> >> pip install git+git://github.com/apache/incubator-airflow.git@v1-10-stable >> >> Or the 1.10 RC tags with eg: >> >> pip install git+git://github.com/apache/[email protected] >> >> Best, >> Taylor >> >> *Taylor Edmiston* >> Blog <https://blog.tedmiston.com/> | CV >> <https://stackoverflow.com/cv/taylor> | LinkedIn >> <https://www.linkedin.com/in/tedmiston/> | AngelList >> <https://angel.co/taylor> | Stack Overflow >> <https://stackoverflow.com/users/149428/taylor-edmiston> >> >> >> On Thu, Aug 9, 2018 at 5:43 PM, Krish Sigler <[email protected]> wrote: >> >>> Got it, will use the mailing list in the future. Thanks for the info >>> >>> On Thu, Aug 9, 2018 at 2:42 PM, Bolke de Bruin <[email protected]> >> wrote: >>> >>>> Hi Kris, >>>> >>>> Please use the mailing list for these kind of questions. >>>> >>>> Airflow 1.10.0 hasn’t been released yet. We are going through the >>> motions, >>>> but it will take a couple of days before it’s official (if all goes >>> well). >>>> >>>> B. >>>> >>>> Verstuurd vanaf mijn iPad >>>> >>>> Op 9 aug. 2018 om 23:33 heeft Krish Sigler <[email protected]> het >>>> volgende geschreven: >>>> >>>> Hi, >>>> >>>> First, I apologize if this is weird. I saw on the Airflow github page >>>> that you most recently updated the v1.10.0 changelog, and I found your >>>> email using the instructions here (https://www.sourcecon.com/ >>>> how-to-find-almost-any-github-users-email-address/). If that's too >>> weird >>>> feel free to tell me and/or ignore this. >>>> >>>> I'm emailing because I'm working with the apache-airflow project, >>>> specifically for setting up pipelines involving GCP packages. My >>>> environment uses Python3, and I've been running into the issue outlined >>> in >>>> this PR: https://github.com/apache/incubator-airflow/pull/3273. I >>>> noticed that the fix is part of the v1.10.0 changelog. >>>> However, the latest version available on PyPi is 1.9.0. On the Airflow >>>> wiki page I read that the project is intended to be updated every ~6 >>>> months, and v1.9.0 was released in January. >>>> >>>> So my question, if you're at liberty to tell me, is can I expect >> v1.10.0 >>>> to be available on PyPi in the near future? If so then great! That >>> would >>>> solve my package dependency problem. If not, then I'll look into some >>>> workaround for my issue. >>>> >>>> Thanks, >>>> Krish >>>> >>>> >>> >>
