enhanced the security page (and added a list of security advisories) #2019
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| =============== | ||
|
|
||
| This document explains how Symfony security issues are handled by the Symfony | ||
| core team (Symfony being the code hosted on the main symfony/symfony `Git |
There was a problem hiding this comment.
I prefer to add symfony/symfony in an inline code-block, the same as we do with Composer packages:
... on the main ``symfony/symfony`` `Git repository`_)
|
Really nice additions to this document - patched into the 2.0 branch without needing any changes at sha: 5bab81f Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on the feedback from an email posted on the Symfony mailing-list, I propose that we enhance our security handling process.
see https://groups.google.com/d/topic/symfony-devs/HeEcBlbjM-c/discussion