Page History

...

Key Decisions

• Updates
  • Airflow v2-0-test branch has already been cut and currently manually rebased on top of the Master. Currently, we don't run CI as the branch is in-sync with Master. As soon as we have a PR / commit that we don't want to have it in 2.0 we will diverge v2-0-test branch from Master and start running tests against it.
  • The upgrade-check PR was merged, we now need to define more rules to add more checks.
• API
  • Progress:
    • Project Board: https://github.com/apache/airflow/projects/1
      • The issues labelled with "Enhancement" are not a requirement for 2.0
    • Endpoints:
      • Task Instance Endpoint is WIP, all the other endpoints have been implemented.
    • Permissions Model:
      • PR has been merged.
      • The next piece of work to be done is migrating existing Views to use resource-based permissions. (Github issue). This is mainly for standardizing the permissions model across API and UI.
• Providers
  • Vote on AIP-8 took place on the mailing list.
  • There is an ongoing discussion on the same thread about SemVer vs CalVer for the Providers package.
    • The people involved on the call were leaning towards SemVer to make a clear distinction about a breaking release. This will potentially increase the work on release managers but some automation around releasing (similar to backport providers) and automation around the generation of the changelog for the providers would make the effort less painful.
  • Version Per Provide: Each Providers package would have a separate versioning i.e. we might release "google-providers 3.1" and "amazon-providers" 3.7 at the same time but the versioning for a particular provider will be independent of other providers.
• DEV
  
  • Would be good to have a release policy on when we can deprecate a feature, our release cadence. A good example is https://docs.djangoproject.com/en/3.1/internals/release-process/#release-cadence
• SubDag Deprecation
  • There is a mailing list thread on whether or not we want to deprecate SubDags in favor of Taskgroups, the majority on the call agreed that we should not deprecate the Subdags yet and wait till people have used TaskGroups and it has feature parity with SubDags.
  • However, we should clearly recommend using TaskGroups compared to SubDags in our docs and state limitations of the SubDags.
• Helm Chart Release
  • Deferred until 2.0 is out
  • Will be available to use from the source code of Airflow on Github but the first official release of the Helm chart will only happen after Airflow 2.0
• Docs
  • Mailing list thread to get some feedback has been created and cross-posted across Slack and Twitter. Once we have enough feedback, Kaxil will create Github issues for them so that anyone willing to help on it can start working on it.
  • A separate section for Upgrading to 2.0 would be ideal, can be a duplicate of Updating.md but with a better structure and more organized.
• UI Changes
  • Github Issue: https://github.com/apache/airflow/issues/10953
  • There are some proposals from Ryan for the UI changes for which he has created some PRs (links below) and in the process of creating few more.
    • Task Instance Modal UX Enhancements · Issue #10944 · apache/airflow
    • Replace JS package toggle w/ pure CSS solution #11035
    • Task Instance header/navigation pattern UX cleanup – Suggestions / VOTE needed here if anyone has strong opinions
• Scheduler HA
  • Reminder: A draft PR for Scheduler HA is available for review. It would be good to get some more feedback from the wider community with their own DEV setup if possible.
• Process
  • Any new PRs would continue to be merged until we complete the items for 2.0 and release alphas.
• NOTE: The Timeline shown on the Planning page will be revisited every week on the Dev Call and updated if needed based on the progress towards the major features of Airflow 2.0

...