nagai/fune
3
0
Fork 0
forked from mirrors/gecko-dev
Code Pull requests Activity

Bug 1822380: Update the documentation that linking security bugs is OK now r=dveditz

Browse source 
Differential Revision: https://phabricator.services.mozilla.com/D172591
This commit is contained in:
Tom Ritter 2023-03-15 13:40:25 +00:00
parent 9730f3f5d5
commit 2683c42a77
1 changed files with 4 additions and 5 deletions
repo.diff.show_diff_stats Download patch file Download diff file Expand all files Collapse all files

9
docs/bug-mgmt/processes/security-approval.rst
View file

@ -41,11 +41,10 @@ Filing / Managing Bugs
filing, instead of filing them as open bugs and then closing later. filing, instead of filing them as open bugs and then closing later.
This is not always possible, but attention to this, especially when This is not always possible, but attention to this, especially when
filing from crash-stats, is helpful. filing from crash-stats, is helpful.
- Avoid linking it to non-security bugs with Blocks, Depends, - It is _ok_ to link security bugs to non-security bugs with Blocks,
Regressions, or See Also, especially if those bugs may give a hint to Depends, Regressions, or See Also. Users with the editbugs permission
the sort of security issue involved. Mention the bug in a comment on will be able to see the reference, but not view a restricted bug.
the security bug instead. We can always fill in the links later after Users without the permission will not be able to see the link.
the fix has shipped.
Developing the Patch Developing the Patch
~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~