Versioning about zpm

[grigorii-horos]

@jjangga0214 Ok. I will release a stable release soon and will support stable zpm syntax. After that, I will make git tags.

[grigorii-horos]

@jjangga0214 What do you mean? I think that versioning isn't needed.

[changwuf31]

It's needed, gotta rollback to commit on Nov 12 to get it working again

[grigorii-horos]

@changwuf31 Maybe, will you create an issue? What problem do you have?

[jjangga0214]

@horosgrisa Hi!
Why do you think versioning is not needed?

[grigorii-horos]

@jjangga0214 I don't have time for multiple versions.

[jjangga0214]

@horosgrisa

Then I think you still can do versioning while not maintaining multiple versions.
Let you just make version tags, and people use it for clone.
In this example below, the tag v1.2.3 is used.

if [[ ! -f ~/.zpm/zpm.zsh ]]; then
  git clone --recursive -b v1.2.3 https://github.com/zpm-zsh/zpm ~/.zpm
fi

Without versioning, people would lose reproducibility on their dotfiles. For example, let's say you make a breaking change of only allowing zpm loads, not zpm load. People's configuration will be broken, once they install zpm on new machine.

To prevent this, you have to maintain both zpm loads and zpm load (theoretically forever).

If you provide SemVer for example, it would be especially useful on this. You can drop support for obsolete syntax and features once you release a new major version.

Though people can use git sha instead of version tag, version provides more info than plain sha. Like if an upgrade to certain commit would probably break something or not.

If you provide changelog with version, it'd be much easier to trace which bug is fixed on which version. This can save people's time as they don't need to search issues as well.