Queue Weekly Status 2015-12-11

Review Queue state (listed add-ons only)

The tables below represent the state of the review queues at different points in time, divided into 3 “buckets” depending on how long they have been waiting. Ideally we want all nominations and updates to be under 5 days, so our goal is to have 100% of reviews on the third column.

Full Review Nominations

             10 days+     5-10 days       5 days-    Total
11/01       119 (84%)       13 (9%)       10 (7%)      142
12/01        83 (70%)      22 (19%)      13 (11%)      118
Now          98 (65%)      25 (17%)      27 (18%)      150

Full Review Updates

             10 days+     5-10 days       5 days-    Total
11/01        43 (67%)      11 (17%)      10 (16%)       64
12/01        19 (31%)       9 (15%)      33 (54%)       61
Now          18 (23%)      31 (39%)      30 (38%)       79

Preliminary Reviews

             10 days+     5-10 days       5 days-    Total
11/01       104 (77%)      18 (13%)      13 (10%)      135
12/01        64 (47%)      37 (27%)      34 (25%)      135
Now          93 (60%)      39 (25%)      24 (15%)      156

Reviewer Contributions

     Nominations    Updates    Prelim.  Admin flag   Info req  Total
Oct    506 (17%)  696 (24%) 1566 (53%)     20 (1%)   147 (5%)   2935
Nov    513 (13%) 1085 (27%) 1984 (50%)     12 (0%)   364 (9%)   3958
Dec      84 (8%)  223 (21%)  707 (66%)      3 (0%)    50 (5%)   1067

Nominations: full review nominations.
Updates: full review updates.
Prelim.: preliminary reviews.
Admin flag: reviews escalated to admin review.
Info req: information requests to authors.


More

For more information on how the review process works, and how you can check your add-on review status, please read An Overview of the AMO Review Process.

Thankfully yesterday a different Admin reviewer finally checked my situation and the matter has been finally resolved after more than 3 months. I still defend that an add-on flagged for admin review should reset its flag when a new version is posted. When a new version is posted the developer most likely has addressed/corrected the reason that lead to the previous flagging (I am such an example) and any reviewer can now review the code itself, and if not then the reviewer can flag it again.