Use https

R/release.r

@@ -20,7 +20,7 @@
 #' of additional questions to ask.
 #'
 #' You also need to read the CRAN repository policy at
-#' \url{http://cran.r-project.org/web/packages/policies.html} and make
+#' \url{https://cran.r-project.org/web/packages/policies.html} and make
 #' sure you're in line with the policies. \code{release} tries to automate as
 #' many of polices as possible, but it's impossible to be completely
 #' comprehensive, and they do change in between releases of devtools.

cran-comments.md

@@ -1,3 +1,9 @@
+This is a resubmission:
+
+* http -> https in link to CRAN policies.
+
+---
+
 ## Release summary
 
 * `check()` now uses `--as-cran`, suppressing just `_R_CHECK_CRAN_INCOMING_`
@@ -18,13 +24,7 @@
 ## R CMD check results
 There were no ERRORs or WARNINGs. 
 
-There were 3 NOTEs:
-
-* checking CRAN incoming feasibility ... NOTE
-  Found the following (possibly) invalid URLs:
-  URL: http://cran.r-project.org/web/packages/policies.html
-
-  This is a false positive - that's not a package URL.
+There were 2 NOTEs:
 
 * checking foreign function calls ... NOTE
   Evaluating ‘dll$foo’ during check gives error

man/release.Rd

@@ -36,7 +36,7 @@ function called \code{release_questions()} that returns a character vector
 of additional questions to ask.
 
 You also need to read the CRAN repository policy at
-\url{http://cran.r-project.org/web/packages/policies.html} and make
+\url{https://cran.r-project.org/web/packages/policies.html} and make
 sure you're in line with the policies. \code{release} tries to automate as
 many of polices as possible, but it's impossible to be completely
 comprehensive, and they do change in between releases of devtools.