-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Add description on how we handle security issues in Airflow #30960
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
Conversation
a3cae4b to
b9d78e7
Compare
potiuk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apply Review comments
75b0047 to
613a236
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unqualified to review yet, but would still like to give a +1 as it looks great to me.
That's still draft - initially discussed in the PMC private@airflow. we are going to get it to the devlist soon. |
This is a proposed description of the security policy we have in Apache Airflow. Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com> Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com>
613a236 to
e9f794c
Compare
Co-authored-by: Vincent <97131062+vincbeck@users.noreply.github.com>
|
AHH... WRONG pr :). |
…pache#30960)" This reverts commit bc7a3ab.
…0960) Proposed description of the security policy we have in Apache Airflow. Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com> Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com> Co-authored-by: Vincent <97131062+vincbeck@users.noreply.github.com> --------- Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com> Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com> Co-authored-by: Vincent <97131062+vincbeck@users.noreply.github.com>
This is a proposed description of the security policy we have in Apache Airflow.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.