I just found out about the not so new namespace mechanism that allows specifying version number. It seems a great idea.
Now in the context of Orbolt, I look at different existing assets but they seem to have just one version.
I wonder how we can manage major and minor versioning where minor would be bug fixes or adding features that doesn't affect existing behavior by default. On the other hand if I want to create a new interface that breaks compatibility I will need a different major release.
Also I'm curious how we can control the pricing of those updates. For example I could decide that a minor update is free because it fixes a bug and another minor would cost some money because it adds quite a lot of new features, and I guess a new major release would be considered as a new tool… although we might like to give a different price for those who already bought the previous version.