Skip to content

Create SECURITY.rst #13564

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.

Sign up for GitHub

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

Closed
vanillajonathan wants to merge 1 commit into from
Closed

Create SECURITY.rst #13564

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions SECURITY.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
Security Policy
===============

Supported Versions
------------------

+---------+-----------+
| Version | Supported |
+=========+===========+
| 3.7 | Yes |

@webknjaz webknjaz May 25, 2019

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vanillajonathan FTR, a lot of projects maintain their own pages with docs so the best thing to do is to redirect people there instead of forcing maintainers to watch out for multiple places to update...

btw, are you sure that RST works for this specific file? I wasn't able to locate this in docs

@vanillajonathan vanillajonathan May 25, 2019

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, reStructuredText works for the security file on GitHub.
Example: https://github.com/apache/airflow/security/policy

@asvetlov asvetlov May 25, 2019

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, it is a shared part of both Markdown and ReST syntax.
The link to devguide page is preferred anyway for sake of keeping Python versions status information in the single place.

@webknjaz webknjaz May 25, 2019

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Andrew, I think it's a good idea to keep all files with one extension for the sake of consistency

@asvetlov asvetlov May 25, 2019

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't care.
Ok with committed code.

+---------+-----------+
| 3.6 | Yes |
+---------+-----------+
| 3.5 | Yes |
+---------+-----------+
| 3.4 | Yes |
+---------+-----------+
| 2.7 | Yes |
+---------+-----------+
| < 2.7 | No |
+---------+-----------+

Reporting a Vulnerability
-------------------------

https://www.python.org/news/security/