You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/06/15 11:43:17 UTC

[GitHub] [airflow] ashb edited a comment on pull request #9276: Add airflow upgrade_check command (MVP)

ashb edited a comment on pull request #9276:
URL: https://github.com/apache/airflow/pull/9276#issuecomment-644076448


   > This make a silent assumption that you always want to migrate to latest 1.10 and then to 2.0
   
   I wasn't planning on making it a silent assumption but the official upgrade path:
   
   1. Update to latest 1.10.x (likely 1.10.12?)
   2. Run upgrade check and apply changes (install required backport providers etc.)
   3. Test this in staging->production etc.
   4. Upgrade staging+test
   5. Upgrade prod.
   
   This approach (latest 1.10.x without warnings, then major upgrade) is based loosely off how Django handles upgrades and deprecation. Let me see if I can find it.


----------------------------------------------------------------
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