Page History

#1: 10 Aug 2020 - Planning & Scoping

...

• Scheduler HA

  • Progress

    • MySQL 8 tests have been added
    • Adoption of orphaned tasks have been added to Kubernetes and to the new CeleryKubernetesExecutor (PR)
    • All (but one) Tests are passing
    • Instructions to run the PR with Multiple Schedulers using docker-compose have been added (link to the comment)
    • Received some reviews on Monday -- Should be addressed by today/tomorrow
  • All Big/Critical Concerns have been addressed (escape hatch for locks, MySQL 8 tests, Moving callbacks to DagFileProcessor)
  • Room to improve code readability which isn't a blocker and would be addressed in follow-up PR
  • Ash is in talks with Kevin to test his Giant DAG to verify Scheduler Performance to address one of Kevin Yang's concern
  • There would be a separate PR for retrying transactions to avoid deadlocks as suggested by MySQL guide on handling deadlocks
• API
  • Kamil and Omair are hoping to complete work on the Task Instance Endpoint PR by the end of this week
  • James is working to map existing permissions to the UI, hoping to complete by end of the week too. Link to PRs
• Backport Providers
  • Backport packages 2020.10.5 will be released without cncf.kubernetes. We will create a separate release for cncf.kubernetes that will address the issues Kamil found in RCs. Link to VOTE thread.
• Airflow 1.10.13 Release
  • Will be released as per the planned timeline (Airflow 2.0 - Planning [Archived]) i.e. Last Week of October. 
• Airflow 2.0 Alpha
  • Revisit on Thursday based on the progress with Scheduler HA & API whether we would be able to release first alpha this Friday.
•  Others:
  • Kaxil to create Github Issues for the feedback received on the Documentation Improvement Thread and create threads asking for VOTES for previously discussed items like removing pickles.
  • Vikram will write up, share and all can review on what we mean by ALPHA and BETAs.

...

#10: 26 Oct 2020

Attendees

Discussion and Key Decisions

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

Agenda for Next Call

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

#12: 9 Nov 2020

Attendees

Discussion and Key Decisions

• 2.0 Beta1
  • Beta: https://github.com/apache/airflow/milestone/10
  • Airflow 2.0.0b1 was cut out on Monday, 9 Nov 2020
• 2.0 Beta2
  • Airflow 2.0.0b2 was cut out on Tuesday, 10 Nov 2020 after a bug was discovered that prevented testing of beta1
  • Testing: To everyone who wants to help with Airflow 2.0.0 beta testing, the following are the main areas we need more help from the community:
    • Kubernetes Executor and KubernetesPodOperator: 
    • CeleryKubernetesExecutor
    • KEDA AutoScaling + CeleryKubernetesExecutor
• 2.0 Beta3
  • Main Purpose
    • Test upgrade from 1.10.12 / 1.10.13 to 2.0.0b3
    • Regression from beta2
    • Providers discovery from beta2
• Separating Upgrade Checks from v1-10-test / 1.10.13
  • A reminder to Committers and any-one interested to add comments on https://github.com/apache/airflow/issues/11112 to decide whether we will keep the source code for the upgrade-check plugin inside airflow-repo or a separate repo

• Airflow 1.10.13

  • Milestone: https://github.com/apache/airflow/milestone/7
  • Should be released in the next 2-3 weeks. 
• New Time for Dev calls
  • The regular Monday dev calls will now happen an hour earlier i.e. 5:30 PM GMT every Monday

#13: 16 Nov 2020

Attendees

Discussion and Key Decisions

• Make KubernetePodOperator Backwards-compatible
  • PR: https://github.com/apache/airflow/pull/12384
  • Release cncf.kubernetes backport-provider package with that PR in to make it backwards compatible with 1.10.x
• Docs
  • Add Docs explaining the different components of Airflow, especially for users migrating from 1.10.x who are not following community news:
    • Providers
    • Backport-providers
    • Airflow Core
    • Helm Chart
    • Docker Image
  • Existing docs for Providers are at https://airflow.readthedocs.io/en/latest/provider-packages.html
• Upgrade Checks
  • Github Issue: https://github.com/apache/airflow/issues/11112
  • The package will be released separately to 1.10.13.
  • However, there is an on-going discussion whether the sources should remain in v1-10-test branch or not.
    • Call to discuss this will happen this Thursday, 19 Nov at 3-4 PM GMT. If anyone is interested to join, use this Zoom link
    • We will also set a date when this separate package should be released and when the alpha/beta will be out to test with Airflow 1.10.x
    • After the decision, this information will be available on the planning page.
• Providers Packages
  • PR for adding new Connections for a Provider using provider.yaml file is out. Each provider folder now contains a YAML file that is used for documentation, PR that introduced it: https://github.com/apache/airflow/pull/12304
  • This will be extended to discover Extra links too.
  • For now, this should be sufficient but in future, we can take a look at Pytest's plugin mechanism suggested by Ash.
• 2.0 Beta3
  • 2.0.0beta3 will be cut by the end of this week
  • Regular betas will be cut every week until we cut RCs

• Airflow 1.10.13

  • Milestone: https://github.com/apache/airflow/milestone/7
  • Jarek has cherry-picked more than 300 commits to v1-10-test that syncs breeze, Helm Chart changes with Master, updated dependencies and test fixes.
  • Kaxil working on further fixes and cherry-picks and we are targeting RCs this Friday

#14: 23 Nov 2020

Attendees

Discussion and Key Decisions

• 1.10.13 to be released this week
• First version of upgrade-check to be released this week
• Composer team + Polidea will test 2.0.0beta3 next week on MySQL 5.7 + MySQL 8
• Don’t need new beta for testing providers, Committers / PMC will test it themselves (Providers’s Packages discovery + Connections / Extra Links)
• Jarek is working on "Registering Extra link & Connections for Providers"

#15: 30 Nov 2020

Attendees

Discussion and Key Decisions

• Bridge release  
  • Airflow 1.10.14 to be built this week and vote started to release next week.
  • Airflow 1.10.13 was released last week, but critical bug discovered after release.
• Upgrade Checks
  • First version of upgrade-check released last week.
  • Additional checks and enhancements to support custom checks being added.
• Airflow DB upgrade
  • The topic of Airflow Database migration was brought up and discussed.
  • We agreed that it would be ideal to recommend this approach for upgrading from 1.10.14 to 2.0, but we need to add a FAQ around how long this database upgrade would take and what possible steps could be taken to reduce this time.
  • For example, by running a script or a DAG to reduce the amount of task history before the database upgrade.
  • A collection of FAQs around this would be important to have as part of the 2.0 release. 
  • Vikram to add issues to capture this.
• Airflow 2.0 Release Candidate: 
  • Overall feedback on Airflow 2.0 core is positive, but polishing still needed.
  • Targeting RC1 build creation to start in the middle of next week.
  • Command line PR not yet merged, but would be good to have in RC1. 
  • Documentation work is ongoing, would be good to clean up before RC1 release.
• Milestone Issue Cleanup
  • Issues currently tagged for 2.0 RC1 should be cleaned up.
  • Those which are not core such as Providers or upgrade scripts, should be tagged for those milestones rather than the 2.0 core RC1 milestone. 
  • All of us to do this cleanup this week and review any open items next Monday. 

#16: 7 Dec 2020

Attendees

Discussion and Key Decisions

• Airflow 2.0 Release Candidate: 
  • Targeting 2.0.0rc1 Wednesday - 9 Dec.
• Upgrade Checks
  • Targeting 1.1.0rc1 Friday - 11 Dec.
• Providers 1.0.0rc1
  • Targeting with 2.0.0rc1 on Wednesday - 9 Dec.
• Airflow 1.10.14

  • 1.10.14rc4 has been cut and submitted for a vote. If vote passes, 1.10.14 would be released on Thursday 10 Dec

• Deprecating Features
  • Follow strict SEMVER.
  • Features won’t be removed until a major version even if they are deprecated
  • Document a policy about that in CONTRIBUTING.rst or somewhere more appropriate
  • Ash to write a proposal about having a major release (e.g 3.0 release) with just removed features

#17: 14 Dec 2020

Attendees

Discussion and Key Decisions

• Airflow 2.0
  • If the vote succeeds, Airflow 2.0 will be released on Thursday, 17 December
• Provider 1.0.0 
  • Apache Airflow Providers 1.0.0 has been released: https://pypi.org/search/?q=%22apache-airflow-providers%22&o=
• Airflow upgrade-check
  • Airflow upgrade-check 1.1.0 has been released: https://pypi.org/project/apache-airflow-upgrade-check/1.1.0/
• Snowflake Issues
  • Snowflake monkey-patches urllib -- which causes issues for example when using S3 logging in 2.0: "'SSLSocket' has no attribute Connection"
  • GH links here: 
  • https://github.com/snowflakedb/snowflake-connector-python/issues/324
  • https://github.com/apache/airflow/issues/12881
  • Escalate and Push Snowflake to fix it and release a new version as early as they can
• Dev calls after 2.0
  • Fortnightly meeting (once every two weeks) each Wednesday at 7:30 PM GMT after 2.0 is released, starting from 6 Jan 2021.
  • Check https://www.timeanddate.com/worldclock/fixedtime.html?msg=8&iso=20210106T1930 to find the time in your Timezone
• Airflow 1.10.13
• 2.0 Beta if we don't release it this Friday
  • Separate beta
  • One to test all the features
  One to test upgrade from 1.10.x