ManuelSchneid3r
commented
2 years ago Its not just numbers. I know that I will seriouly break the API soon. I'd like to release a major version too, but in the end we would have a v1 for some months maybe even years. And then have to switch to v2, since plugins of this version are incompatible to the future one. Sure I dont like this zero/alpha image, but going over to have to bother about backward compatibility is worse. I am working on albert 0.18 for over a year now. A the moment™️ I am sketching concepts, code some of them, dropping them and so on. Certainly I could have released a 0.19, 0.20, 0.21, 0.22… But then again I'd have to do the real stuff like deployment, issue tracking etc. Time eaters, but actually the real reason is that most probaly plugin maintainers, which are extremely rare anyway, would be pissed of of having to change code every few weeks. I dont want to bother supporters for as long I cant deliver something sophisticated. I appreciate your encouraging words but especially 0.18 will be nowhere near mature. That why I though about a 0.18-pre for some betatesting. If this thing is out I'll think about it again. Regards
Why?
I've been using albert for years now, since around 2017. It's a daily driver on different devices and I never had any larger issue, even when switching to Wayland in 2018. I just noticed the last release is stil a
0.17.x, but I claim that albert is stable for a long time and very much worthy of having a1.0.0release.See https://0ver.org/about.html for more info.
Many thanks to all contributors.
How?
A new git tag I guess?