From murdoch.duncan at gmail.com  Thu Mar  6 21:22:48 2014
From: murdoch.duncan at gmail.com (Duncan Murdoch)
Date: Thu, 06 Mar 2014 15:22:48 -0500
Subject: [Rd] version numbers for CRAN submissions that give
	warnings/notes
In-Reply-To: <5318CEDF.4050605@yorku.ca>
References: <5318CEDF.4050605@yorku.ca>
Message-ID: <5318D918.6090501@gmail.com>

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 cran at 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



[Rd] version numbers for CRAN submissions that give warnings/notes
Duncan Murdoch