Security/Firefox/Security Bug Life Cycle/Security Advisories: Difference between revisions

Jump to navigation Jump to search
Line 52: Line 52:


Go through and review it. For the first pass, I recommend edits be made directly on the advisory.txt attachments. However, certain edits will not be possible to do there. Specifically: adding (or removing) the description field from the top of the document and editing the list of reporters in the rollup advisory.
Go through and review it. For the first pass, I recommend edits be made directly on the advisory.txt attachments. However, certain edits will not be possible to do there. Specifically: adding (or removing) the description field from the top of the document and editing the list of reporters in the rollup advisory.
=== Review it yourself ===
* We use the past tense when writing about vulnerabilities
* The titles of bugs do *not* use Title Case, they use Sentence Case.
* Function names and objects should be enclosed with <code> tags
* JavaScript not javascript
* use-after-free not 'use after free'
* Check if there are no community members on the rollup, and if so, remove that bit


=== Get review ===
=== Get review ===
124

edits

Navigation menu