I understand the inclusivity need, and that's perfectly fine. However I am
afraid community will not have a process (and people) to keep the
documentation up-to-date - it will almost immediately become obsolete and
useless - we have like 10 commits coming in every day, most of them
including some d
Since we are just about to release 1.10.4 and my team is gearing up to some
"summer" cleanup of GCP operators - I would like to revive this thread and
reach some binding conclusions on this finally
Kamil prepared this document:
https://docs.google.com/document/d/1F8zve5S78DXcjpPttW89HnqT0M0iKjT6fo
Hi Jiajie, Kamil,
My intention with a multilingual website is to make the project accessible
to users around the world, grow inclusive community, and drive the adoption
of technology faster among groups that speak and understand English less
than well. As you said, Chinese community benefitted fr
I agree with everything Kamil said - we need to split the docs into:
- website/landing page (simple, static, slow-changing, multi-language,
managed by designated people)
- Tutorial/Documentation (fast changing, every contributor can change
and update it, automatically generated from t
Thanks Kamil remind me in https://github.com/apachecn/airflow-doc-zh/issues/65
I agree with you multi languages point, I think Airflow leading page should
have multi languages
But for the documentation, I think it hard to up to date
I’m one of contributor of https://github.com/apachecn/airflow-do
Thanks for testing.
On 1) everyone should run upgradedb on every upgrade. The behaviour of not
running it wasn't great.
2) I thought we set deprecation on the ES logging config vars, except we put
the depreciation under the wrong section:
https://github.com/apache/airflow/blob/1.10.4rc3/airflo
+1 (nonbinding) to the release, it fixes a lot of UI issues we've been
seeing lately. Though two notes:
1) Tasks were unscheduleable until I ran an upgradedb due the default pool
change.
2) I got crash loops because I based our custom logging file off of the
previous version's template. The chang
Hi all,
I've just been working on updating many of my macros to include logic to handle
holiday calendars. There was a small mistake in one of the macros and I found
it very difficult to debug, I'm not sure where a default logger in the plugins
would log out to and there was no obvious way to r
