@embeddedt and @kisvegabor: Thanks for the responses. I’ll make sure to take a look at the Changelog.
I can understand the problem with the extra overhead. It’s a problem that a lot of projects have (including the one where I’m a bit more active: RTEMS). For open source projects time without funding always has to be interesting so that someone want’s to do it.
Please also note that I don’t have a problem with bugfixes in the releases between 7.1.0 and 7.10.1. What I’m worried about are new features like the “Style caching” in https://github.com/lvgl/lvgl/commit/41fd83e1d326da37210fc8bdbdc851e79c1683eb. These are bigger changes that might introduce new bugs and therefore would need extensive new testing of the application.
From a user perspective it would be ideal if such changes would be on another branch. Meaning: One branch with “stable but old” 7 version where bug fixes are cherry picked but no new features or big structural improvements are added. And one with lots of improvements that would sometimes in the future will result in a version 8.0.
Again: I understand why it doesn’t exist. Reason is that there is not enough unfunded time. And at the moment I’m not sure how it could be made funded time. But I think especially for industrial projects it would be a great feature.
BTW: I think the question about a LTS version in Version lifecycle and LTS versions had a similar background.