Description
Skipping versioning the project was an intentional choice that allowed us to focus on the minimal usable version very fast. Now that we have users starting to try PyScript and engage with the project, it's basically an urgent need for us to choose a versioning system for PyScript so that we can better speak in terms of planning & roadmap, support and feedback (users can refer to specific version when bug reporting), and discussions.
An important aspect to keep in mind is that PyScript is still in its very early stages. So, we should highlight that the expectations should be that think can often break until we reach a level of maturity and stability.
For these reasons, I'd like to propose that we adopt Calver as a versioning convention. It seems to be a good fit in terms of capturing the progression/maturity of versions in time and allows us to not overpromise on stability as we roll out new versions (especially important for where PyScript is today vs the interest shown by the community). It also makes it easier in terms of not having to overthink version numbers when we are introducing new features vs. feature changes vs bugfixes, etc..
Semver is the other obvious option to take into consideration since it's pretty much the standard for a lot of projects but, for the reasons described above, I'd put my vote on Calver.