potiuk commented on pull request #8807: URL: https://github.com/apache/airflow/pull/8807#issuecomment-629042359
Hey @ashb @kaxil @mik-laj @feluelle . I think I have finally solved all the small quirks - including some extras (like apache-beam) messing with the installation. This one contains all the fixes discussed above plus: * we do not have to modify setup_backport_packages.py to change version or add rc1/rc2. Package version is now the same as the generated readme version and you can add `--version-suffix rc1` manually when preparing packages. This way from exactly the same commit we can generate rc1/rc2 etc. without having to modify anything (we could use the same technique to generate main airflow package BTW). * Documentation in BACKPORT_PACKAGES.md is updated to include this simplified process * we excluded some of the google packages (bigquery ones) from the google provider release. We (@turbaszek ) are running now big rewrite of the bigquery operators and they will not be backwards compatible, so we think it is bettter to exclude them from this release (we will release this and some new operators in a few weeks - at the same time testing the single-package releases. * When you prepare packages - by default when you do not provide the date, by default it is +5 days - this is mostly used in the CI job. The CI job will prepare (and upload to files.io) readmes for all packages - this way we can see the release notes for packages that need to be released. I will improve it further to only show and summarize the packages that "need release" - i.e. those that had some changes since the last release (but I will add it later). I want to have a single page/report showing - "those are the changed backport packages - maybe we should release some of them"? ---------------------------------------------------------------- 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]
