On 04-Apr-19 2:53 AM, Richard Kimberly Heck wrote: > On 4/3/19 5:52 PM, Uwe Stöhr wrote: >> Am 02.04.2019 um 03:02 schrieb Richard Kimberly Heck: >> >>>> You see why I insist that proper Windows support is only possible if >>>> the >>>> whole process, compilation, installer building and testing the >>>> installation is run on different Win systems. >>> No, I don't see why it matters whether we compile LyX on Windows or on >>> Linux, and nothing you said seems to address that. >> I just gave you two examples why only installing LyX on a Windows PC >> could unveil problems: > You said I have to *compile* LyX on Windows. Of course I *install* LyX > under Windows to test it. > > As I also said, it is my intention to release 'testing' versions which, > presumably, will be installed by people on different systems. I'm hoping > to get to this fairly soon. Problems that turn up that way will be fixed. > > I agree, of course, that it would be better if the person responsible > for the Windows installer was a Windows user. But, at the moment, we > don't have anyone who is (i) willing to take that on and (ii) willing to > abide by decisions of the LyX team. > > Riki > > Hello,
The new approach in software engineering is conduct agile DevOps cycles, which results frequent releases of the software. This may be problematic for programs like LyX, which depends on many other open-source sofware (e.g. Python, MikTeX, ImageMagic, etc.. ). One solution to this problem may be implementing agile DevOps cycles for LyX itself. There are tools like Jenkins that can be used for automated testing and release. Maybe, LyX team can invest to such technologies to be able to be synced with the surrounding software. B. Erkus -- ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ Please bottom-post. Start your reply here:
