On 03/20/2013 07:31 PM, Thiago Macieira wrote: > Can we please agree on cleaning the dashboards up? Or, if we've agreed, can we > do it? > > My dashboard is unusable. For a few months now, I have stopped my daily look > at the "Review Requests" section. As a result, I have missed important reviews > of new features that should maybe be in 5.1, but will probably miss the > deadline because my comments come in too late. Tough luck if you were > affected. > > I don't care how we're going to solve this, but can we please agree that we > need to solve it and *do* solve it? To be frank, I really don't care if people > feel offended that their patch that they haven't updated for 4 months gets > "abandoned". If someone can find a better word, say so. If someone knows > whether it's possible to create a separate state in Gerrit and this person > *can* do it in our Gerrit installation within two weeks, say so. > > Otherwise, let's use the solution we know of. > > > Until that happens, here's how I will operate: > - I will look at my "Review Requests" dashboard once a month, > time-permitting > This does not mean I will review everything. Complex reviews will probably > be skipped. > - I will react to pings on IRC (but reserve the right to do it later) > - I will react to Gerrit emails that arrive while I am awake > When I wake up, there are about 100 unread emails in the Gerrit folder > alone, most of which will be ignored
Indeed, I don't either look at the dashboard these days, however I've found reacting to the Gerrit emails sufficient, since then I'm notified about the following: - new changes that I need to review - comments on existing changes - changes failing in CI - changes being merged, so that I can close the task I'm guessing part of the reason for the large amount of traffic (100 unread emails as you say) atm is that an auto-test failure will send one mail for each task you're subscribed to that's in the progress of being staged. -- Samuel _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
