Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Airflow 2.0.1:
  • Providers Release
    • Next set of Providers will be released next week once https://github.com/apache/airflow/pull/13767 is merged with appropriate SEMVER version (e.g Google would be a major release while ES would be a patch release)
    • Backport Providers will be released for the ones that have some significant changes after or at the same time as the providers
    • Snowflake released a new version (v2.3.8) and the Snowflake provider which will use this version will be released too as currently all versions for Snowflake providers are YANKED.
  • Upgrade Checks
  • Helm Chart Release
    • We need to agree on what we call the first version: 0.0.1 vs 2.0.0
    • We need to review the current Helm chart before it is released as a lot of changes have been merged since it was first merged.
    • Current Test Coverage is not that great - ideally, we would like to cover more test cases before it can be released 
    • We hope to release it after 2.0.1 so bugs fixes are in by then and 2.0.1 can become the default version for the Helm Chart

Next Meeting Agenda

3 Feb 2021

Attendees

Name

Company

Kaxil NaikAstronomer
Vikram KokaAstronomer
James TimminsAstronomer
XD Deng-
Jarek PotiukPolidea
Daniel ImbermanAstronomer
Ry WalkerAstronomer
Dennis AkpenyiAstronomer
Philippe GagnonAstronomer
Dennis Kromhout van der MeerAstronomer
John JacksonAmazon

Summary

  • Airflow 2.0.1:
  • Providers Release
    • Providers will be released on Feb 8
    • Backport Providers should also be released as along with Providers, assuming vote passes
  • Upgrade Checks
    • 1.2.0 will be released soon after Airflow 2.0.1 once the vote passes
  • Apache Airflow 1.10.15TBC
  • Improve Airflow Observability
    • John to create Github Issue around what metrics would be useful to avoid failures early from an Operational point of view. Based on that we can discuss and recommend using existing metrics or add missing metrics.
  • Make Doc contributions easier
    • We should have a separate section in CONTRIBUTING.rst for users who want to create PR for only doc-changes.
    • Currently, it is difficult for new contributors to understand how to add cross-links, using sphinx, building docs locally, debugging spelling-check errors.
    • Adding some recipes/templates in the CONTRIBUTING.rst with code to create Cross-references, adding links, spell-check, etc using Sphinx would make it easy.