DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
- 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
Name | Company |
Vikram Koka | Astronomer |
| Daniel Imberman | Astronomer |
Ry Walker | Astronomer |
Jarek Potiuk | Polidea |
| Tomasz Urbaszek | Polidea |
| XD Deng | |
| Kosteev | |
| Mary | |
| Bin | |
| Rafal |
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 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 on any open items next Monday.