Change default version for new projects to 0.1.0

[bluthej]

I just started using huak (heard about it on the Python Bytes Podcast), and I really like the idea!

I noticed that new projects created with huak new have a default version of 0.0.1. The semver 2.0.0 specification suggests starting at 0.1.0 (which is what cargo defaults to BTW). I suggest to adopt the same convention.

I do realize that this is a matter of preference but I think it's not a bad idea to try to be consistent with the semver spec :)

[cnpryer]

Thanks for this suggestion. I'll give it some thought. I'd prefer to lean towards specifications (especially semver), so atm I'm thinking this is a good idea.

My original thought process is really from experience. I always like to start with a 0.0.X release to create a grace period to help mold a more stable first 0.1.X.

[bluthej]

I totally understand, I guess it's just a matter of what you are used to. I think the people who wrote down semver have in mind that the 3rd digit is really just for bug fixes, and in the pre-1.0 period you can do whatever you want. It's the 1.0.0 that sets the stage for stability. Sounds like your approach is a bit different so I'll let you decide what you prefer :)

[Yura52]

I'll add my two cents. Formal standards (such as the mentioned "semver") is a good thing unless they are in conflict with what people actually do :)

In my personal experience, 0.0.X is a popular way to mark the state of the project as something like "ready for sharing as PoC for enthusiasts, not so ready for wide adoption". I come from the field of Deep/Machine Learning, and the recent examples that come to mind are torcheval and tensordict (note how the 0.1.0 released is described as "First official release"). In my personal project, I follow the same strategy: DeLU. However, all this may be just a personal bias :)

Anyway, I think the pre-0.1.0 stage of the project is a thing overlooked by the semver rather that a "bad practice that diverges from standards".