Page History

...

• Alpha2
  • Released on 26 Oct along with the providers too
• Providers 
  • Vote in process for Backport Providers 2020.10.29 - VOTE THREAD
  • Pending items:
    • Extra link registration of Providers to core Airflow
    • Docs
      • Split documentation from Core Airflow Docs
      • Installation of Providers
      • FAQ Section
        • Upgrading apache-airflow and providers package
        • Why do Providers have separate versioning than apache-airflow core?
        • Why extras to install providers? And what version of providers are installed when installing providers via Extras
• KubernetesExecutor Update:
  • Draft PR to allow passing pod_template_file for overriding Pod Specification: PR Link
• Airflow 2.0 Updating Guide
  • https://github.com/apache/airflow/blob/master/UPGRADING_TO_2.0.md contains the information required to upgrade to 2.0 from 1.10.x. This is a WIP doc and the idea is that this place should be a single place for Users to look at when they want to Upgrade to 2.0 so it should contain all the details in a digestible manner. If anyone has any suggestions on this document please create a Github issue or bring it to the mailing list.
  • ToDo:
    • Add a dedicated step to install the latest backport-providers before Upgrade.
    • Details around how long 1.10.x & backport providers will be supported should be added to Upgrading doc – Github Issue Link
• 2.0 Beta1
  • We will wait until Friday to see how we are progressing i.e. if all the bugs found in alpha2 are fixed or not: https://github.com/apache/airflow/milestone/10. 
  • If we are not done by Friday, we will move the beta1 release to next week
• Airflow 1.10.13
  • Milestone: https://github.com/apache/airflow/milestone/7
  • Let's triage the Milestone and start the release process for 1.10.13

#11: 2 Nov 2020

Attendees

Discussion and Key Decisions

• 2.0 Beta1
  • Milestone: https://github.com/apache/airflow/milestone/10. 
  • We will cut out beta1 at some point this week as all the outstanding items in the milestone should be done in a day or two.
  • While announcing the beta we will ask users to check out the documentation too, so that we can identify missing gaps.
    • We need to specifically add instructions (Both Slack and Email) for users who find this missing notes to at least creates Github Issues describing what is missing and ideally if they can create PRs to fix it.
    • Python wheel, tar.gz and Dockerfile for beta1 will be published to facilitate easier testing
  • PRs to enable Black and Pyupgrade across the code-base will be rebased and merged before publishing beta1. This might cause some PRs to have conflicts and we will recommend users to squash all commits in their PRs so that it is easy to resolve conflicts as it should just be the matter of running pre-commit hook for black and pyupgrade.
• Separating Upgrade checks from 1.10.13
  • upgrade-check tool will now be released separately from Airflow 1.10.13. The main reason for deciding to do so is that we will be able to add more upgrade checks even after 1.10.13 is released.
  • Github Issue: https://github.com/apache/airflow/issues/11112 . Please add any suggestions or ask any question over there. If needed, we can do a separate call otherwise async discussion will continue on that Github issue.
• Airflow 1.10.13
  • Milestone: https://github.com/apache/airflow/milestone/7
  • Triage and Release process has started for 1.10.13. We aim to release it in the next 1-3 weeks. 
  • Releasing in in the next two weeks will allow people testing upgrade from 1.10.13 to Airflow 2.0.0beta2 which would be critical.