Plans for a tagged version

[mpe85]

First of all, thanks for all the work done so far on this great library.
Are there any plans to publish a tagged version, like discribed here https://go.dev/blog/publishing-go-modules?

[kortschak]

There are no plans, but I'm not wedded to working on pseudo semver. If there is a good reason to move to tagged versioning I'm happy to do that.

[mpe85]

As soon as the API is stable it makes sense to tag a v1.0.0, and if in some future you decide to break the API you could tag a v2.0.0.
This way it would be easier for people to see if an upgrade, e.g. from 1.0.0 to 1.0.1, does not break the API and its safe to upgrade. Besides that it's also easier to reference a tagged version in one's go.mod file.
With those pseude version numbers v0.0.0-xxx you never know what you get when doing an upgrade without having to look at the source code of the project.

I think it's not really much effort since you only have to create a git tag and push to github.

[kortschak]

In theory, that's how it works, but modules versions >1 are irritating. I'd be happy to tag at v0.1.0. I don't anticipate breaking changes, but I don't have the time to deal with v2 modules if they do happen.

[mpe85]

Sure, it's totally up to you how to handle this. A v0.1.0 tag would at least help to better integrate with golang modules.

[kortschak]

I'll see when I have time to do that. Probably when I update the tested versions. It's worth noting that the ev3go packages have been opted into modules for a few years now and pseudo versions are perfectly legitimate way to do that.