[R-pkg-devel] new version jumps in minor?
Rolf Turner
ro||turner @end|ng |rom po@teo@net
Tue Nov 5 00:31:55 CET 2024
On Mon, 4 Nov 2024 16:33:40 -0500
Toby Hocking <tdhock5 using gmail.com> wrote:
<SNIP>
> Version jumps in minor (submitted: 2024.11.2, existing: 2024.1.24)
It looks to me that you are setting your version numbers in an
unorthodox manner, which could/will confuse the living Drambuie out of
people.
I conjecture that you are setting your version number to represent the
relevant date. E.g. 2024.11.2 means 2 November, 2024 and 2024.1.24
means 24 January 2024.
In my understanding, the usual convention is for the version number to
be of the form l.m.n (or l.m-n) --- major.minor.patch (or
major.minor-patch). The date should be specified in the *Date* field of
the DESCRIPTION file.
It probably does not matter a hell of a lot. "Writing R Extensions"
just says that the version number should be "a sequence of at least two
(and usually three) non-negative integers separated by single ‘.’ or
‘-’ characters".
However you might save yourself some "NOTEs" by adhering to the
"l.m.n" convention and incrementing the components sequentially.
cheers,
Rolf Turner
--
Honorary Research Fellow
Department of Statistics
University of Auckland
Stats. Dep't. (secretaries) phone:
+64-9-373-7599 ext. 89622
Home phone: +64-9-480-4619
More information about the R-package-devel
mailing list