[GitHub] [airflow] potiuk commented on a change in pull request #19867: Initial commit for new Breeze project

[GitBox <gi...@apache.org>]

potiuk commented on a change in pull request #19867:
URL: https://github.com/apache/airflow/pull/19867#discussion_r758227000



##########
File path: dev/Breeze/requirements.txt
##########
@@ -0,0 +1,4 @@
+click
+pytest
+pytest-xdist
+rich

Review comment:
       We might consider that indeed.
   
   I think there is a certain simplicity that the code to manage development is inside the repo with the code. It solves a number of problems, and especially mkes it easier to use versioning. I would treat that as an option to follow in the future and the way how we "release it" eventually when we get to the point where it is is "ready to use". 
   
   One potential problem with it is that you have to actively "install" the latest version if you want new features and by having everything in the same repo, of the code that is used to manage it, you have it "by default" (which also means that  it is less stable). 
   
   Keeping it under "dev/Breeze" folder does not preclude having a separate package and PyPI release. There could be two modes of runnign Breeze - one from the sources, and one from the package. 




-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org