Dear all, We are closer to 2.2.0rc1. The following are the issues that I think we should address before 2.2.0rc1 (and 2.2.0 final).
Regarding the tickets that we have with a 2.2.0 milestone: #9892 Peter stated [1] that the patch is not necessary for compilation with MSVC 2010. It seems the majority opinion is to release rc1 (and final 2.2.0) with Qt 5.5.1 compiled with MSVC 2010. Uwe, are you OK with that? Is there a critical Qt bug that only affects LyX if we compile against 5.5.1 and does not affect LyX when compiled with 5.6.0? Although 5.6.0 would bring new features, such as better support for HiDPI, I think stability is more important. We can provide unofficial installers using Qt 5.6.0. #9992 It is a crash because of a screen management tool. Because it is due to external software, I don't think we should consider this a rc1 blocker. There is a regression from the user perspective, and it would be nice to know whether different Qt versions lead to different behaviors. For example, if the crash is still experienced with 2.2.0rc1 compiled with Qt 4.8.6 (which I think is what 2.1.x was compiled with), then perhaps we can figure out what the change in LyX's code was. #9963 Although this is a regression, we cannot reproduce and I don't think it is a blocker so unless someone has an idea I think we must postpone. #9985 We don't know what the problem is but there is a workaround and no one can reproduce, so I do not think this is a critical bug. #10017 Sub-menus do not expand on Windows. This would be a critical bug but only one user experienced the issue on beta2. Note that alpha1 did work for the user. I think we should see if the user also sees the bug with rc1 and for which Qt versions (assuming we do provide multiple unofficial installers with different Qt versions). #10019 Guillaume fixed some ui regressions. The patch seems short and logical and Stephan has tested it on Mac. I would still like to see if someone can test it on Windows before it is included. If anyone with Qt knowledge can take a look at the patch, that would also be nice. I think normally I would not want any .ui changes in at this point (for the reasons I listed on that ticket), but since they are fixing regressions it is hard to resist. #10027 The 2.2.0 part of this bug just involves adding an "obsoleted" note. Other topics that are not targeted to 2.2.0. - I do not understand if we need to do something for #9979? - Georg has provided a patch to improve building with Python 3 here: https://www.mail-archive.com/search?l=mid&q=ncf3fj%24gqh%241%40ger.gmane.org Helge has tested that it works for him. Does anyone +1 the patch? - There are layouts that we want to update so that they work with newer versions of the class/style files that have been recently released. - Regarding replacement of "long table" by "multi-pages table", José kindly made progress but we are still missing a full patch. José's progress is here: https://www.mail-archive.com/search?l=mid&q=25133064.0sqmE3gEfi%40jamatos - Enrico has provided a patch regarding separators here: https://www.mail-archive.com/search?l=mid&q=20160313003332.GA8700%40giove Even though it is a file format change, I think it would be nice to include because otherwise users will have to get used to new behavior in 2.2.0 and then get used to changed behavior again in 2.3.0. I do not understand the issue though since I rarely use separators. Guillaume or José since you seem to understand the issue, can either of you give a +1 to the patch? - What am I missing? Scott [1] https://www.mail-archive.com/search?l=mid&q=56E2B241.9030001%40gmx.net
signature.asc
Description: PGP signature
