I propose that from now until we get the next 1.1 prerelease out (post
beta 2), performance work should be a second priority. We're currently
at 45 open bugs on 1.0 branch, 103 on 1.1 branch (trunk...and 3 are high
priorities for 1.1b2), 8 scheduled for "1.x", and 143 unscheduled.
I believe we need to work on reducing the number of bugs. Performance is
looking great by most accounts, and we still need to accept performance
bugs as they come in. But performance should be secondary for a while
behind getting functionality, stability, and uniformity (of API, etc)
fixes done.
This would include performance of Joni itself, which we need to look at
getting a stable, official release of.
Of course any really egregious performance problems can get a higher
priority, and any fixes related to memory leaks are top-priority above
general functionality bugs.
Seem like a reasonable plan for now?
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
