Re: "Subversion" revision numbers as 0.01

However, I have one question: I've read somewhere, or seen an example, of people using their CVS revision numbers as the last part of their module $VERSION numbers, so that you might have something like 1.02_13 where the _13 is the CVS revision number, which is automatically inserted when making a commit (I think).

If you follow this style you'll have problems releasing modules to CPAN since an "_" in the version string marks it as a developer release.

Comment on Re: "Subversion" revision numbers as 0.01_blah

Replies are listed 'Best First'.
Re^2: "Subversion" revision numbers as 0.01_blah by rvosa (Curate) on Jun 07, 2005 at 19:24 UTC
That was kind of the idea: there'd be "stable" releases without the "_", and developer releases.	[reply]
Re^3: "Subversion" revision numbers as 0.01_blah by adrianh (Chancellor) on Jun 12, 2005 at 22:56 UTC
That was kind of the idea: there'd be "stable" releases without the "_", and developer releases. Ah, okay. Fair enough I guess. Personally I'd find it rather confusing since I'd expect a "_42" suffix to mean that this was the forty second developer release, rather than it being the forty second revision of some repository I'm never going to see :-)	[reply]