On Wed, Jun 11, 2025 at 3:39 PM Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote:
> Le 11/06/2025 à 19:45, Joel Kulesza a écrit : > > All, > > > > I hope you're doing well. I'm sorry to be silent for so long, but I've > > enjoyed following the list and many developments discussed within. > > Hi Joel, > > Nice to hear from you. > > > I'm still happily using 2.3.2 but want to begin using the 2.4 series, as > > such I went to the LyX website and noticed the typo in the top news post > > <https://www.lyx.org/News#item1>: > > Are you really using 2.3.2? Why did not you try to upgrade to 2.3.8? > > Just curious. > JMarc, I am (i.e., we are). I'm part of a software development team with members who use macOS, Linux, and Windows. So, a coordinated switch to ensure we have as robust and self-consistent behavior as possible across our OSs is a non-zero effort. There is also accompanying "cost" in terms of accommodating any unexpected change in behavior, configuration, behavior, etc. For the features we rely on, 2.3.2 has served well and continues to (and none of the bugs fixed through 2.3.8 have negatively affected us). Further, because of the concurrent release schedules that LyX maintains, a change to 2.3.8 would have been somewhat concurrent in time with a move to 2.4.x such that any change might as well be to the more featureful version. But, to permit that, I wanted to let some of the 2.4.x bugfix patches land and have the mailing list discussions settle to avoid adopting any misbehavior (to the extent possible). As I said, I've enjoyed keeping an eye on the lists, and I appreciate the work that the LyX development team puts into this software and its community. On a related note: you may be amused (horrified?) to hear that we only recently moved off TeXLive 2018 (because it similarly did everything we truly needed). I thought this might invite a question, which is why I was perhaps overly specific. But to that end, I hope this satisfies your curiosity and also helps the team understand one of the modalities that LyX users / user teams might operate with. We've now been successfully using LyX, as a team within a version-contolled software-development environment, for over five years with no apparent end in sight and it's been an important tool for us to democratically maintain our documentation. Thank you, Joel P.S. Pavel—thanks for the quick fixes of those typos!
-- lyx-devel mailing list lyx-devel@lists.lyx.org https://lists.lyx.org/mailman/listinfo/lyx-devel
