Am Samstag, 30. Oktober 2021, 00:35:59 CEST schrieb Albert Astals Cid: > What's the story with kdevelop-pg-qt?
kdevelop-pg-qt has been released on its own separate schedule. Being a rather feature-complete tool and only used for the soon to be legacy qmake plugin support in KDevelop, there is no need for changes there. > What's the plan for auto-increasing version numbers on release? So far the prepared fallback plan is to use own major & minor version and for the patchlevel use the calculated "compact release service version number" (doing a 2-digit padding for the micro number though to ensure ever increasing numbers also with KDE Gear Beta & RC versions). There is on-going discussion/tinkering to find a way for nicer patchlevel numbers, or perhaps just switch completely to KDE Gear version and find some other way to describe plugin ABI/API version. No promising candidates for now, so either we sort something out in time latest for 21.12 RC, or just stick with the fallback plan for the time being. You might be referring to my considerations on #kde-sysadmin about a new ever- increasing KDE Gear release version number variable to e.g. derive a patchlevel from by an offset. That is for now back to the drawing board (TODO section, >= y 2022), needs more thought and also investigations into the use cases of other plugin API providing products in KDE Gear, to have a proper generic solution one day. Cheers Friedrich
