|
4 | 4 | #' `r lifecycle::badge("deprecated")` |
5 | 5 | #' |
6 | 6 | #' `release()` is deprecated in favour of [usethis::use_release_issue()]. |
7 | | -#' We no longer feel confident recommrding `release()` because we don't use it |
| 7 | +#' We no longer feel confident recommending `release()` because we don't use it |
8 | 8 | #' ourselves, so there's no guarantee that it will track best practices as |
9 | 9 | #' they evolve over time. |
10 | 10 | #' |
| 11 | +#' If you want to programmatical submit to CRAN, you can continue to use |
| 12 | +#' [submit_cran()]. |
| 13 | +#' |
11 | 14 | #' @template devtools |
12 | 15 | #' @param check if `TRUE`, run checking, otherwise omit it. This |
13 | 16 | #' is useful if you've just checked your package and you're ready to |
@@ -228,23 +231,13 @@ cran_submission_url <- "https://xmpalantir.wu.ac.at/cransubmit/index2.php" |
228 | 231 | #' Submit a package to CRAN |
229 | 232 | #' |
230 | 233 | #' @description |
231 | | - |
232 | 234 | #' This submits your package to CRAN using the web-form submission process. |
233 | | -#' After submission, you will receive an email asking you to confirm submission |
234 | | -#' - this is used to check that the package is submitted by the maintainer. |
235 | | -#' |
236 | | -#' You may prefer to use `submit_cran()` indirectly, by calling [release()] |
237 | | -#' instead. `release()` performs many checks verifying that your package is |
238 | | -#' indeed ready for CRAN, before eventually asking for your confirmation that |
239 | | -#' you'd like to submit it to CRAN (which it does by calling `submit_cran()`). |
| 235 | +#' To complete the submission you will need respond to the email sent to the |
| 236 | +#' maintainer email address. |
240 | 237 | #' |
241 | | -#' Whether to use `release()` or `submit_cran()` depends on the rest of your |
242 | | -#' development process. If you want to be super cautious, use `release()`, even |
243 | | -#' though it may be redundant with other checks you have performed. On the other |
244 | | -#' hand, if you have many other checks in place (such as automated checks via |
245 | | -#' GitHub Actions and the task list generated by |
246 | | -#' [usethis::use_release_issue()]), it makes sense to use `submit_cran()` |
247 | | -#' directly. |
| 238 | +#' We generally recommend using this part of the process defined by |
| 239 | +#' [use_release_issue()]; this process maximizes the chances of a successful |
| 240 | +#' submission. |
248 | 241 | #' |
249 | 242 | #' @template devtools |
250 | 243 | #' @inheritParams release |
|
0 commit comments