On 2024-10-28 12:56 p.m., Georgi Boshnakov wrote:
Also, v1.1 = v1.1.0:
package_version("1.1.0") > package_version("1.1")
[1] FALSE
package_version("1.1.0") == package_version("1.1")
[1] TRUE
If you adopt the 2-digit versions but decide to keep the possibility for
3-letter ones for minor fixes (bugs; fixing CRAN NOTES, minor bugs etc.),
always use the four-digit development versions, e.g. 1.1.0.9000 after release
of 1.1, to keep the possibility for 1.2 or 1.1.1 for the following release.
That's one strategy, but it's not the one I use. I generally increment
the 3rd digit whenever I make a bug fix or minor change to the source.
I won't necessarily release every one of those, but they'll be available
on Github, and if I get a bug report that has been dealt with, I can say
things like "that was fixed in version 1.2.12. You can get 1.2.14 from
Github using this code: ...., or wait a couple of months until a later
version is released on CRAN". I dislike Hadley's x.y.z.9000 scheme.
Duncan Murdoch
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel