On 06/03/2014 2:39 PM, Michael Friendly wrote:
It often happens that I submit a new revision of a package, say
mypkg-1.0-10, from R-Forge
to CRAN after running R CMD check locally and looking at the log files
on R-Forge.
But R-Forge has the devel checks disabled, and I get an email from CRAN
pointing out
some new warning or note I'm asked to correct.
OK, I correct this and commit a new rev to R-Forge. But, is it still
required to bump the
version number to mypkg-1.0-11 before resubmitting to CRAN, even though
mypkg-1.0-10
did not make it there?
To do so means also modifying the DESCRIPTION, NEWS and
mypkg-package.Rd files even for a minor warning or note.
That sounds like a question about CRAN policy, so I think you'll need to
write to c...@r-project.org for an answer. But I would assume it could
cause confusion if you submitted another identically named tarball, and
I'd recommend bumping the version number.
Duncan Murdoch
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
