Any tagged releases like v0.1.0 planned?

[ali-ramadhan]

Would be helpful to be able to depend on a specific tag/release without having to worry about whether the main branch has changed.

[odunbar]

Yes this is an excellent point, particularly as linking packages is annoying when they do not have published versions.

Perhaps @jakebolewski has more input in what else would be involved in getting things ready for a first release.

[ali-ramadhan]

It's pretty easy to tag new releases: https://github.com/JuliaRegistries/Registrator.jl#install-registrator

I'm happy to help if I can!

I don't think anything needs to be done to get things ready since CI is already in place and the package name should pass the automated checks.

You can always continue tagging new releases as new features are added and bugs are fixed. In fact, some people would argue for tagging new releases with every PR: https://www.oxinabox.net/2019/09/28/Continuous-Delivery-For-Julia-Packages.html (although this might be a bit extreme, but I guess I definitely lean towards frequent tags)

[jakebolewski]

I think we first need to tag and register EKP to make managing the dependencies easier

[odunbar]

I'd like to think that once we have some starting docs for each this would be a natural time. Perhaps early next week is not unreasonable for this aspiration.

[glwagner]

Any update? Note that tagging a release doesn't really make a package more "visible", it's just a slight convenience for users.

[ilopezgp]

@glwagner @ali-ramadhan Sorry for not addressing this issue earlier, the first release is here!