issue-priorities.md

AMP GitHub Issue Priorities

The AMP team is using the below priorities and guidelines to make it easier to order issues by the level of attention they need. These guidelines can give you also a good overview of when to expect updates or closure of issues.

If you would like to give a hint regarding the priority of the issue you can add the appropriate priority GitHub label. Note that the priority may be changed as the issue is triaged based on the project's roadmap and backlog.

Priorities & Guidelines

Priority	What it means	Guidelines for Bugs	Guidelines for FRs
P0: Drop Everything	Outage Critical production issue	Drop everything until this is fixed Should be assigned and accepted within 24 hours of filing Provide regular bug update on status and ETA of the fix, once every day after acceptance Fixed in 7 days (next release or patch release, whichever is sooner)	We do not use P0 for FRs
P1: High Priority	Breakage of a critical feature or user journey Highly significant feature	Should be assigned and accepted within 48 hours of filing Should be updated by the team once every week after acceptance Fixed within 30 days or updated with explanation and timeline	Implementation guidelines: 2 weeks Feature requests are not P1, unless a situation develops where the lack of the feature is significant user problem (e.g. lack of the feature may block a significant number of AMP implementations)
P2: Soon	Breakage of a non-critical feature or user journey Major usability problem (users frequently do the wrong thing) Important feature	Best effort Fixed in a quarter	Implementation guidelines: 1 Quarter Generally higher priority feature requests These are mostly features that have been specifically scheduled to meet our roadmap</li
P3: When Possible	Minor usability problem Polish Minor features	Best effort	When possible