Hi,

I'm working on an application (a thing with a "main" function) that has
a user-visible version.  Since the internal modules of the project do
not have any backwards compatibility between versions, I've been tagging
releases with versions that the Go tools won't recognise (galene-0.3
instead of v0.3).

How would I tag the versions so that people can depend on my code in
their projects without implying any form of backwards compatibility when
the user-visible version goes beyond 1.0?  I'm thinking of shifting the
user-visible version number one position to the right, e.g.

  galene-0.4 -> v0.0.4
  galene-1.0 -> v0.1.0

Is that the recommended usage, or are there better ways to achieve that?

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/87mtvx47dw.fsf%40pirx.irif.fr.

Reply via email to