Issues are tracked at bugs.chromium.org.
Issues that do not have a contributor actively working on them may be in one of three states:
Issues being worked on should change the status to let others know it may be resolved in the near future:
Closed states resolve an issue:
|Priority||Target Response Time||Resolution|
|Priority-0||1 working day||“soon”|
|Priority-1||5 working days|
|Priority-2||30 working days||best effort|
As explained on the support page the Gerrit community aims to achieve the target response times that are documented above, but there IS NO guaranteed Service Level Agreement.
The new web interface built in Polymer. Issues in this component are actively managed by PolyGerrit maintainers involved in the daily development efforts.
Related to the change metadata in Git project, which is migrating Gerrit off the SQL “ReviewDb” database.
Issue is unique to the
googlesource.com family of servers, including gerrit-review.googlesource.com. This covers both administration support required (e.g. correct a broken user account) and issues unique to the server's plugins (e.g. authentication/web sessions or secondary index).
Issues for a plugin project hosted under plugins/. Actively developed plugins may have their own subcomponent.
All bugs require to specify the Gerrit version the bug was found in. This helps to categorize bugs and clean up stale bugs.
The engineer working on fixing an issue can set “TargetMilestone” to specify the Gerrit version they expect to deliver the fix.