Abdelrazak Younes wrote: > Georg Baum wrote: >> Abdelrazak Younes wrote: >> >>> Friendly reminder Jose ;-) >>> >>> Just wanted to add that, for my needs, 1.5.0 is basically "ready". Sure, >>> we have some bugs left but nothing that can stop someone to use it on a >>> daily basis, at least not me :-) >> >> "some" bugs is good. There are a lot, upon them 34 regressions, 13 of >> them are new in 1.5. > > We are not forced to solve 1.4 bugs too to release 1.5, are we?
No. But several users still use 1.3, because 1.4 has too many problems for them, and we already promised several times that they won't get these problems with 1.5. Therefore, the more important regressions of 1.4 should be solved in 1.5, e.g. http://bugzilla.lyx.org/show_bug.cgi?id=2552 http://bugzilla.lyx.org/show_bug.cgi?id=2581 http://bugzilla.lyx.org/show_bug.cgi?id=2555 http://bugzilla.lyx.org/show_bug.cgi?id=2594 http://bugzilla.lyx.org/show_bug.cgi?id=1814 http://bugzilla.lyx.org/show_bug.cgi?id=2554 http://bugzilla.lyx.org/show_bug.cgi?id=2529 http://bugzilla.lyx.org/show_bug.cgi?id=1973 http://bugzilla.lyx.org/show_bug.cgi?id=2758 This list is partly based on my own preferences, and partly on feedback on the users list. > IIRC, you proposed to not branch 1.6 soon after 1.5.0 and continue the > bug fixing for a while. I think it is a good idea. Yes, I still think that we should do that. >> And if we would add the regression tag to each bug that is >> a regression it would be even more (we have 97 open bugs in 1.5 >> currently). >> >> Not all of these bugs need to be solved for 1.5.0 (some of them are >> enhancement requests), but some of them are really tricky. > > The problem is that most developpers do not know how to solve these (me > included). That is indeed a problem. We need more people like Richard who come and wade their way through the code and actually understand it. >> IMO 1.5.0 is not ready at all (but of course we need the next beta, and I >> predict that it will not be the last one). > > > Please list the show stoppers. http://bugzilla.lyx.org/show_bug.cgi?id=3291 http://bugzilla.lyx.org/show_bug.cgi?id=3332 http://bugzilla.lyx.org/show_bug.cgi?id=3346 http://bugzilla.lyx.org/show_bug.cgi?id=3320 http://bugzilla.lyx.org/show_bug.cgi?id=3043 http://bugzilla.lyx.org/show_bug.cgi?id=3449 http://bugzilla.lyx.org/show_bug.cgi?id=2959 http://bugzilla.lyx.org/show_bug.cgi?id=3256 http://bugzilla.lyx.org/show_bug.cgi?id=3231 http://bugzilla.lyx.org/show_bug.cgi?id=3404 http://bugzilla.lyx.org/show_bug.cgi?id=3427 http://bugzilla.lyx.org/show_bug.cgi?id=3321 Some not in bugzilla: - the \inputencoding problem found by Dov. - the nomencl compatibility problem If you want something to work on: 3427 was introduced by you with the metrics reorganization, and it happens always for me. > I don't share your pessimism, especially > if we are to compare current SVN with the state of 1.4.0 when it was > released. That is not a good comparison. 1.4.0 should not have been released in that state, otherwise we would not have users still using 1.3. If we don't regain the stability of 1.3 with 1.5.0 we will probably never recover from the lost reputation. And maybe one reason for being pessimistic is because I know that I won't have much time to participate in the bugfixing (I am glad if I can finish the already promised fixes). Another reason is that several people are discussing (and changing) fundamental design principles of LyX (e.g. the separation of frontend - kernel via the lfun machinery), or doing some 'cleanup'. Now is definitely not the time to even think about either of that. Or political discussions like the place of debug.h. This eats a lot of time with no outcome. And of course the fact that beta2 is not out yet is no good sign either. Georg
