Also, is it the case that if user’s do have issues with it we could suggest really simple work-around of just not opening the dashboard? (I am not saying this would be something we should rely on but just as a worst case fallback. I realize that it would be too late for users to deal with existing reviews, but I suppose they could delete them — though I don’t think we’ve solved the issues of erasing existing review models, so that could still bloat the workspaces even after deleting them.)
Sam, Jacques, let’s open a new bug (“Strategy for dealing with large number of automatically added tasks”) to discuss; a) if this is a practical concern b) if it is really solved by 430315 and c) if not, is there any *really* simple* change we can make to address it. If we can clarify that to everyone’s satisfaction then I could be convinced on +1 — but I’d like to hear Steffen’s opinion on this one as well. To be clear, this hasn’t actually been released in the wild yet for any significant (beyond reviews devs) testing? One concern I have, which I raised on bug 430315 in March and never got a response to, is that the dashboard may add a very large number of reviews to users' task lists without them even knowing, and this can seriously impact the performance of task list filtering.
I think it'll be a shame if we don't contribute the dashboard to Luna but the fact is I'm not confident that it won't cause problems for users and therefore I'm leaning towards voting -1 on contributing it to Luna. I'd like to see it in Luna RC1 (which is Sept. 26) provided the outstanding concerns get addressed.
Sam
mylyn-reviews-dev mailing list
mylyn-reviews-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylyn-reviews-dev
-- Miles Parker Senior Software Engineer, Tasktop Committer, Eclipse Mylyn, Virgo http://tasktop.com skype: milestravisparker
-- Miles Parker Senior Software Engineer, Tasktop Committer, Eclipse Mylyn, Virgo http://tasktop.com skype: milestravisparker
|
