I open this thread according to https://forum.sailfishos.org/t/sailfish-community-news-25th-february for further discussion
For me as a developer, it’s a bad thing to be presented with a fait accompli during early release.
Python changes do 3.8 - bam my application does not work anymore - and many others.
Just a new library release? Bam several apps (in openrepos!) uninstall because of missing libraries.
I would appreciate some news like: “We will have changes in openssl, python, libraries blabla which might break your solutions in the next release.” Then a developer will have time to react before the end user sees problems.
For me the early release is a test for the plattform itself. And most of the time the problems with own applications can only be found by guessing not by interpreting the changelogs. And some developers without the experience e.g. in python version changes or library bindings might have bigger problems why their code does not work anymore.
Yes, you only support harbour side libraries to be stable but only sort of. Thinking about PodQast/Gpodder IconMenus which did not work anymore because there were new elements in Silica with the new release. And the harbour concept does not really work, otherwise openrepos would not be necessary.
For a professional application handling there must be some instance for checking up, it the old stuff will work. There is a testing instance for new applications/application versions pushed into harbour. But there is no instance which checks the actually stored apps in harbour against new releases.