jscheffl commented on PR #35868:
URL: https://github.com/apache/airflow/pull/35868#issuecomment-1872228582

   @potiuk Yes, before re-basing another 10 times, I'd like to get this off the 
plate and merged. So your advise and prep help might help:
   
   - I assume all feedback consistently points that the migration tool shall 
not be in the Airflow mono repo. If there would be any kind of other GIT repo 
that you can create or point to to bring #35861 to then this would be a good 
pre-requisite. This PR needs to point to migration tool in docs. I do not have 
a strong opinion where to store the migration tool but woul dbe better also not 
pointing to my personal account.
   - This PR is quite large, the debate around migration script clean is not 
settled. I would be OK to revert. Maybe separating into at least two PRs might 
make discussion easier. (PR1: Removal of support form core + breeze / PR2: 
Clean up of leftovers in migration tooling)
   - Development advise in regards: Would it be OK to merge this to main "soon" 
or for better patch maintenance of 2.8-line do we need to keep this removal as 
a PR open for longer? Otherwise nobody really made a review, and I don't want 
all the efforts being dropped/wasted as actually I had positive intention as a 
follow-up of the vote to clean-up MSSQL but missing support for review here.


-- 
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-unsubscr...@airflow.apache.org

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

Reply via email to