potiuk commented on pull request #11487:
URL: https://github.com/apache/airflow/pull/11487#issuecomment-707444084


   Hey @kaxil (and others).
   
   I implemented all that is needed to release Airflow 2.0 tomorrow (err today) 
separated into providers.
   
   It looks like we will be able to release allpha1 already split into 
providers.
   
   * airflow is now stripped of providers
   * providers are generated automatically
   * documentation is updated on how to generate the providers and how to 
upload them to pypi
   * tests are automatically run in the CI for both - backport and regular 
packages
   * for regular provider tests i also build airflow 2.0 whl package and 
install it in breeze - then i install all packages separately
   * the documentation is comprehensively updated. I went through the 
instructions and managed to generate all packages I also released an example 
package to test-pypi : 
https://test.pypi.org/project/apache-airflow-providers-zendesk/  - I added 
@kaxil and @ashb to manage the packages.
   * I also tested it manually and was able to install airflow separately and 
provider packages separately
   * currently all packages are in version 0.0.1
   
   There are couple of things missing (but they can be added later)
   * extras are not yet connected to providers (so provider packages will not 
be installed automatically when installing an extra 
https://github.com/apache/airflow/issues/11464 (I could likely get it in 
tomorrow mid day)
   * process of versioning is not yet defined - I asked @ashb to help with 
that: https://test.pypi.org/project/apache-airflow-providers-zendesk/
   * the "registration" of providers in core is not yet done (but it is not a 
blocker)
   * All the remaining issues for AIP-8 are in 
https://github.com/apache/airflow/projects/5
   
   
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to