Use 0.1.0 as default first version in mix new task

[aquarhead]

Triggered from this tweet: https://twitter.com/HugoGiraudel/status/738694810350014464

This is your friendly reminder that semantic versioning starts at 0.1.0, not 0.0.1. You can’t start with a bug fix.

Also documented in Semantic Versioning's FAQ (http://semver.org/#how-should-i-deal-with-revisions-in-the-0yz-initial-development-phase)

The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.

[whatyouhide]

I am a bit torn on this. While 0.0.1 may not be a valid release, that may be the intention here: when you create your package from scratch, you usually don't "release" anything. In order to

start your initial development release at 0.1.0

you have to have a release first, or at least this is how I interpreted this.

Quickly looking at tooling in other languages, we have:

• Bundler uses 0.1.0 when you run bundle gem my_new_gem
• One example of Node package skeleton uses 0.0.0 (which is an interesting approach 😃, since it doesn't start with a bugfix but with a bogus version right away)
• Haskell's stack starts with 0.1.0.0, which I'm not sure what it represents but for the scope of this discussion it would seem to be 0.1.0

So, not sure, but we have a bunch more info now :).

[aquarhead]

Should have looked at some other project management tools first..

I think the key here is "start", you start on a project, not bugfixing an empty skeleton.

Another thing is when mix new it also fills README.md with instructions of how to use the (to-be-published) library: https://github.com/AquarHEAD/elixir/blob/1cb56b05f982b02a5dc43a6474cd79719cce6a94/lib/mix/lib/mix/tasks/new.ex#L197-L212

I think it will mislead people if not changed.

[josevalim]

❤️ 💚 💙 💛 💜

[josevalim]

I think following semver advice is a good idea.