potiuk commented on issue #51545: URL: https://github.com/apache/airflow/issues/51545#issuecomment-2983258257
BTW. Is there a reason we are not discussing that in devlist? I think this is a very important topic - how airflow will be split into distributions and something that will haunt us if we do it wrong. While yes it could be that "whoever takes on the task" will make it and applies their own understanding, anyone doing it might miss a number of consequences - so I think we should design the split and discuss it and possibly even create an AIP for that. There was a document started by @ashb that we initially commented on. Is there any reason we do not want to share that document and start discussing on it in devlist? I believe it's very clear (at least for me) what problems are still to be solved with `task.sdk` - circular dependencies of various sorts mainly. And I think when we apply more people's wisdoms and ideas we might come up with a better design and we can discuss long term consequences - especially that there are a number of peopel (including me but also @eladkal @bugraoz93 @gopidesupavan and @amoghrajesh and others who had been experiencing, witnessing and solving problems with common packages and cross dependencies. This is not a simple thin and if we do it wrong, it will really haunt us. So I'd say we should start devlist discussion on it. What's stopping us from that ? -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
