I’m probably going to first release it at something like 0.7, which will then be in the mode @OvermindDL1 suggests. @devonestes is totally right about the work so far though. Somebody would try to build something “real” on apis that I need to rearrange, rework, or whatever, and they would complain about the churn in the codebase.
I used to describe developing software projects as similar to making Jello. You’ve picked the flavor you want, but at first is all liquid and stirring around. Then it starts to harden, but is still mixable. Then it hardens more, generally keeps its shape, but bounces all over the place. Then the vibrations reduce until is is stable. Note that it never stops moving completely, it just gets very predictable.
To me, calling it 0.7 reflects that there is still room for feedback and possible breaking changes, but that the worst of the bouncing is in the past. Won’t call it 1.0 until it feels nice and presentable as a dessert or maybe in a nice fruit salad or some other analogy that is now past it’s original meaning.
