On Sat, Oct 10, 2015 at 07:50:59PM +0100, Guillaume Munch wrote: > Le 10/10/2015 05:01, Scott Kostyshak a écrit : > > > >1. Do you agree that the master branch is stable and that we should move > >soon towards releasing an alpha? I saw a couple of reports of crashes > >that could not be reproduced (Guillaume, I think you had one recently? > >[1]), but these seem to be the normal amount to me, so nothing too > >concerning. > > I could not reproduce it. Overall it crashes less than 2.1.4, especially > thanks to Enrico's works on math macro updating. Identifying the cause of > 9362 also helped.
Good. If you can reproduce or even if you just have a one-time backtrace, let us know so we can play the guessing game. > >2. What are the bugs that should be fixed before we release 2.2.0? > >Please note which of these bugs are regressions. Please note also if you > >are volunteering to work on the bug yourself. > > http://www.lyx.org/trac/ticket/9785 : regression Uwe can you look at this? > http://www.lyx.org/trac/ticket/9362 : the problem has been quite precisely > identified, a decision has to be taken. Even if it is just "let's warn the > users". Can you start a separate thread on lyx-devel summarizing the long discussion and providing a couple of options that we can discuss for 2.2.0? It seems that only you and JMarc have discussed it so it would be nice to get opinions from others. > http://www.lyx.org/trac/ticket/7790 : a layout format change. This is about > custom TOCs in the outliner and navigation menu, e.g. lists of "Sweawe", > "TODO" and "FIXME" insets (recent new modules), and it is apparently very > easy to do. There is a design proposal and I offered to do the back-end part > (already done for the list of figures). People who care about this > enhancement, this is your last call if you do not want to see it postponed > to 2.3. >From what I understand, you are willing to do the back-end part if someone else does the layout implementation. Is that correct? If so, then the question is whether either Jürgen or Richard has the time and interest to work on it. > Most of the other bugs can be postponed IMO. > > There are also several not-recent crashes involving QTimers not shown on the > 2.2 milestone (8964, 8261, 6713). I noticed that there is a habit of setting > single-shot timers instead of member QTimers. This is a problem, because the > single shot timers are not destroyed with the calling object, so the timer > may operate on invalid data or even call methods of destroyed objects. This > is easy to fix, I know how to do it, but I cannot guarantee to find the > time. Nice, I like patches that fix multiple issues. Unless you fix this in the next week or so, please post the patch to the list and get a couple of +1 from other developers before pushing. I don't have a high enough understanding to know how risky the fix will be, even if as you said writing the fix is easy. > >3. What features would you like to still implement for 2.2? Which of > >these features could not be put off for a 2.2.x release (e.g. requires a > >format change)? I know it is hard to estimate, but how long do you think > >it would take for you to implement each of your proposed features? > > I have been working on a final enhancement to the source panel > (http://www.lyx.org/trac/ticket/4725) for 2.2. But if it is not done this > week-end I will have to postpone it anyway. Stay tuned. Sounds good. By the way, thank you for the fixes to the source panel you have already done. They are a nice improvement. Scott
