Security/Tracking protection/Bug triage: Difference between revisions
Jump to navigation
Jump to search
m (Rephrase the de-duping sentence.) |
(Use "entitylist" throughout) |
||
| Line 15: | Line 15: | ||
# Set a priority on the bug: | # Set a priority on the bug: | ||
#* '''tp-product''': none | #* '''tp-product''': none | ||
#* '''tp- | #* '''tp-entitylist''': P2 | ||
#* '''evangelism''' keyword: P5 | #* '''evangelism''' keyword: P5 | ||
Revision as of 20:39, 14 September 2017
How
- Look through all Firefox::Tracking Protection bugs and webcompat.com issues linked from the breakage metabug looking for things we can fix:
- Platform bugs should be moved into Toolkit::Safe Browsing
- Server-side bugs should be moved into Cloud Services::Server: Shavar
- Close any unreproducible bugs with WORKSFORME.
- Check that breakage bugs include the offending blocked resource in the comments.
- Tag bugs with the list that causes the breakage in the whiteboard field.
- tp-base for the standard list
- tp-content for the strict list
- Mark bugs that have the same root cause (e.g. Facebook videos are blocked on site X) as DUPLICATE of one another.
- Add the tp-entitylist whiteboard tag if the breakage could be mitigated by expanding the entity whitelist to linked domains owned by the same organization.
- Add the evangelism keyword to any bug that needs to be resolved by the site owners (e.g. to avoid relying on trackers for their site's functionality to work).
- Tag feature requests and bugs that require a product decision with the tp-product whiteboard tag.
- Set a priority on the bug:
- tp-product: none
- tp-entitylist: P2
- evangelism keyword: P5