Yeah, nothing is concrete at all. It's probably a cycle or two away. The qml bits will probably survive mostly as-is, just with the python backend getting replaced (eventually, some day, maybe). So it doesn't hurt to fix bugs now, because a) users are using this stuff right now, and b) it'll be used as a reference for the re-write, so we don't want to accidentally port bugs from python into go ;-)
Yeah, nothing is concrete at all. It's probably a cycle or two away. The qml bits will probably survive mostly as-is, just with the python backend getting replaced (eventually, some day, maybe). So it doesn't hurt to fix bugs now, because a) users are using this stuff right now, and b) it'll be used as a reference for the re-write, so we don't want to accidentally port bugs from python into go ;-)