-
Notifications
You must be signed in to change notification settings - Fork 14.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move Backport Providers docs to our docsite #11136
Conversation
Nice. I guess we shoudl also cherry-pick it to the v1-10-test branch for 1.10.13. i can do it. |
(cherry picked from commit f4ec1f6)
It seems to me that we have several products and each product has its own documentation. We therefore should update the index of our documentation - |
@mik-laj -> maybe create an issue for it? That's an interesting proposal that seems like a major doc restructuring - impacting all the stages - updating, building, releasing. And one that might finally speed up the documentation building process. Sounds like an interesting candidate for 2.1 :) |
@potiuk will do. |
Yea I like the proposal @mik-laj too |
I created an issue: #11152 |
(cherry picked from commit f4ec1f6)
(cherry picked from commit f4ec1f6)
(cherry picked from commit f4ec1f6)
(cherry picked from commit f4ec1f6)
The Backport Providers guide is more suitable for docsite. I have improved grammatical errors wherever necessary to while moving it. This also makes our README.md a bit lighter.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.