Hello everyone.
As a developer, I understand the reasons why the elimination of the 1.x compatibility layer is proposed, and in the end I share them, but I have to say that this is particularly a big problem for me.
I think the approach should not be 1.x compatibility layer = yes, or 1.x compatibility layer = no. But how to keep bindings 1.x working for users who still need them, either via 1.x compatibility layer or another method, such as having another OH 1.9 instance linked by MQTT. Always looking for the simplest and least traumatic solution for everyone, developers and users.
In my case, I have spent several years writing in the free time the binding “Cardio2e”, based on openHAB 1.x. Last year I finished writing the documentation, and it was finally included in version 2.4. I fear, as a result of this thread, that it is possible that the binding that has taken so much effort to write is no longer functional in version 3.x; and that all my effort has been left in broken sack. And at the moment I do not have time to rewrite the code (quite complex, by the way) and adapt it to the new model of bindings 2.x. I know at least 30 users, including myself, that we would make use of this binding and that we will have to remain anchored in openHAB 2.x if finally a formula is not provided to integrate it.
It occurs to me that perhaps someone could write a migration guide to 2.x for developers of bindings 1.x, which minimizes the rewriting effort to the maximum, even having an archetype that facilitates the work of migration.
Greetings.