If you do a query like this: https://gerrit.iotivity.org/gerrit/#/q/status:open+project:iotivity+is:mergeable+AND++NOT+label:Code-Review%253D-1+AND++NOT+label:Code-Review%253D-2++AND+NOT+label:Verified%253D-1
that is, mergeable, no downvotes, and did not fail verify you get 140 patches (click next near the bottom to see other screenfuls, by default you get 25/page). The "mergeable" qualification means all of these have been touched recently (mostly within a week), so there are probably a bunch more that would also qualify, but have "bit-rotted" due to other merges and at the least need rebasing. That feels like a lot to me and leaves me wondering how we could do better at keeping the backlog down. The question in the subject line is whether we're bottlenecking on reviewer time. Admittedly, this snapshot number is a little deceptive, Phil has fired up a bunch of patches for 1.2 (not quite sure why) and any tagged for 1.3 are not going in right now as the release is being prepared. Thoughts? _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
