mik-laj commented on pull request #9502: URL: https://github.com/apache/airflow/pull/9502#issuecomment-650715607
@potiuk It's a good idea, but I'm not sure we have to do it now. Temporarily storing automatically generating the code will allow us to solve teething problems more easily. We can transfer all the code to new repositories for each client before the release of Airflow 2.0. Then the specification will be stable all the time and will not change. The whole team will also have much more experience with automatically generated clients, so there will be fewer problems with them. Now previewing changes in clients while changing specifications would be very helpful to prevent unknown problems. We also don't have to publish development versions in a separate repository. It seems to me that publishing artifacts on Github Actions will be sufficient and will also allow clients to download on forks and pull requests. Which will help solve teething problems. ---------------------------------------------------------------- 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: us...@infra.apache.org
