On Fri, Apr 15, 2011 at 5:11 PM, Martin Pool <[email protected]> wrote: > There are other simplifications that I think would probably improve > the user model more though, like unifying fixreleased and > fixcommitted, or confirmed and triaged, or various other old bugs. > One reason I think they would have a higher payoff is that everybody > dealing with bugs hits them, whereas using multiple tasks is a more > advanced use.
I have a few thoughts here. Firstly I hesitate to prioritise things purely on user impact - sometimes the balance between effort and rewards is linked, sometimes its not :). In this specific case, we'd save ~6% of the table row size, which would help significantly on table scans, which would help performance - and everyone feels that. Beyond that though, *everyong* runs into tasks on multiple series except for the /most/ simple projects. I agree that multiple tasks on one bug is rarer ( 89512 | many 651228 | one ) but having multiple series on a project is much more common: every user of Launchpad for Ubuntu bug management runs into this case; and its this case that we would be simplifying. Interestingly, many products only have one series: 3637 | many 18698 | one but if we assess how many bugs are in each project and then group by type we get this: 210391 | many 97824 | one So - I think the overwhelmingly common experience on Launchpad is dealing with projects that have multiple series that their bugs fall into. -Rob _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
