[GitHub] [airflow] potiuk commented on issue #6960: [AIRFLOW-XXX] Add tips for writing a note in UPDATIND.md

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

potiuk commented on issue #6960: [AIRFLOW-XXX] Add tips for writing a note in UPDATIND.md
URL: https://github.com/apache/airflow/pull/6960#issuecomment-569599081
 
 
   I think it is far too many details at this stage (especially for 2.0 where we accumulate changes and there might contradicting or overlapping changes to do. We might revert some changes after we test it or we might want to combine some of the changes in which case there will be completely different migration procedure. 
   
   I believe we should add all the details (especially migration procedure) before releasing 2.0.0 - when we will be writing the migration tool described in https://issues.apache.org/jira/browse/AIRFLOW-6390. 
   
   This will be the right time to provide examples and test the migration process I think. 
   
   Also we have the past entries which do not have all the details anyway, so we will have to do the exercise anyway.
   
   For me current level of details we have in UPDATING.md was enough.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services