Abdelrazak Younes wrote: > The export in thread is a _real_ usability improvement. As a user I > would be very furstrated to go back to single threaded LyX. And as for > the unicode transition, the multithread export enabled us to clean up > the design and source code of many things in LyX. > > I recently was forced to go back to 1.6 and it was a very bad experience > to wait for pdf updates when fine tuning the appearance.
There is no need to argue about the usefulness, I agree 100%. Unfortunately the current status is that the feature is not finished. Peter and Pavel seem to think that it is possible to finish it in a nonintrusive way, while I thought that this was not the case. > Last point is: I didn't had a single crash for months, except when I > followed a recipe for crash to solve a bug. Trunk is more or less as > stable as 1.6.0 now and very much stabler than 1.5.0. So IMO we can > release now. Unfortunately a single user experience does not say much if we are talking about thread problems, since they highly depend on external stuff like OS, other running processes etc. It is possible that a non-thread-safe code works perfectly on one machine, while it crashes several times per hour on another one, maybe with a different use pattern. Thread-safty is definitely an issue that causes problems in practical usage, even if it is often quite difficult to reproduce those problems in a test setup. > That being said, I understand the stability concern so, if this really > is a problem, we should offer an rc option to disable it by default. The > rc option could be enabled again for 1.6.1 when all bugs are fixed. This > way we can release 1.6.0 right away. No RC please, because you would need to label it "Make export faster but allow it to crash in some cases". Either the threaded export works, then it should be enabled, or there are known problems, and then it should be disabled. Georg
