As Michael reported that we making progress concerning the open bugs I started 
a bugzilla cleanup:

Results:

- We had 103 UNCONFIRMED bugs and now 59, that means I was able to reproduce 40 new bugs. I didn't understand all bug reports, so if somebody has some time might have a look especially at the older unconfirmed bugs.

- We have 105 confirmed bugs, not fixedintrunk, that are were already in the 
LyX 1.3.x series

- I set some bugs to milestone 1.5, the ones that seem to be the most annoying ones. Of course this selection is not objectively, so feel free to drop the milestones. Currently we have 73 confirmed bugs that aren't marked fixedintrunk with the milestone 1.5.0 (I have not targeted them all to this milestone!)

- We have currently 15 confirmed crashes, 9 of them are also in LyX 1.4.x

- We have 23 confirmed bugs that are a regression to LyX 1.3.x

All of the bugs listed above aren't enhancements


Conclusions:
(Don't beat me for the following.)

We either introduced in LyX 1.4.0 much more bugs than in previous releases or our user base has grown and so we get more bug reports. I assume the latter is the case. To make LyX 1.5 more stable than LyX 1.4.0 I think we should, besides the known crash bugs, fix some of the regressions, if this doesn't imply file format changes, and as much as possible bugs targeted to 1.5.

LyX 1.5svn is much faster than LyX 1.4.3 and I use it now for daily work.
I see that every day some more small opimizations are committed. Concerning this let me post this controversial question: Shouldn't we better concentrate now on stability issues and bugfixing than reaching the absolute maximal speed and cleanest ever possible code?

Of course there are some performance problems left, see e.g. bug 3099, but I mean that many of the open bugs can easily and quickly be fixed if a bug is in the working field of a developer.

regards Uwe

Reply via email to