On 24 September 2019 at 11:43, Roy Mendelssohn - NOAA Federal via R-package-devel wrote: | A few days ago I had to resubmit because an external URL I was using in my vignette changed and the nightly builds were issuing warnings. This morning a user reported a bug. I have the fix and a new version, but the test machines, and I suppose it will also be true of CRAN, are unhappy about the interval since last submit. Should I just submit the new version anyway with a note in cram-comments that this is a bug fix.
Yes: AFAICT these are recommendations to not overburden CRAN. And I have hit two distinct types: - more than six uploads in six months (which happened when an upstream package was hyperactive) which lead me to space uploads out a little more as "one a month should be plenty" indeed - less than seven days since the last upload (which lead me to just wait two days on a very recent "better bug fix to a bug fix" upload I made, and then got me the very automated processing) You can look in the R sources for what the cutoffs are (which is how I confirmed it was 7) and act accordingly. So yes, in sum, explain what you do to CRAN -- and some human will generally do the Right Thing. (And big thanks and kudos to CRAN for the increased automation documented in the short update at the end of the most recent R Journal issue. Very impressive, and very well done.) Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
