In IRC today, Alec brought up the question: when do we throw in the
towel on some of these performance bugs for 0.6?
The bug council has been closing bugs when they meet the target or are
no longer perceived as significant usability problems. We also haven't
marked any performance bugs as blocking, because we don't think any of
the performance problems are terrible enough to block the release. (Hey,
that is a small victory!)
We are leaving some performance bugs open though. In particular we have
a bunch of bugs that make the app feel sluggish with big calendars. It
is worth continuing to invest time in these bugs as long as we are still
making progress. At some point, though, there is no progress to be made
without non-trivial architecture changes.
A proposal for punting these bugs: if two people have looked at the use
case thoughtfully and have determined that no reasonable work can be
done without non-trivial architectural changes or other risk, then we
can move the bug to 0.7.
Comments?
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
