I am fighting with the same thing as well 
I agree with @watou for the 1.x compatibility. Especially if you want your binding to be used by people who set up their OH server and forget about it until next release… Which should be the majority of users if OH is successful for a broad user base.
I actually have two bindings I am developing, one adapter to owntracks ( New binding for mqttitude / owntracks ) and another for custom-built hardware ( Proper source place for a binding with (very) limited audience ). For both, I will target OH2 as I like hacking on the bleeding edge.
Also, I hope that we can move the OH2 release faster now that we have a larger maintainer group which can help Kai on upcoming issues.