Tag new version?

[df7cb]

Hi,

the latest commit here fixes a lot of compiler warnings, would you consider tagging a new release? That would help with updating the Debian packages.

Thanks!

[begriffs]

Hi Christoph, thanks for your help with packaging. I can tag a release, but wondering what tag name would make most sense. Currently, the tags match the extension's schema versions. For instance, tag v0.0.2 has pg_rational--0.0.2.sql in the repo. I wonder if there should be a v0.0.2-1 tag since it's not corresponding to a schema version bump? Does Debian have a standard name for this sort of thing?

[df7cb]

I think the release version should have one more component than the SQL-level extension version, for example 0.2.0 and 0.2. That way, there is no need to bump the SQL extension version for code-level-only fixes.

Debian doesn't care about the format of the release version as long as the number is increasing. We can cope with - in version numbers, but it complicates a few things since it's already used to separate the -1 Debian package version, so it should best be avoided.

I've been thinking about blogging about that for maybe 10 years, so I guess I should finally do that 😅 .

[df7cb]

For the concrete case now, I would suggest to tag 0.3.0, make the SQL version 0.3, and then hope it saves a SQL-level bump next time.