CRAN release TODO
Open
@mjskay is already working on this.
Since Jul 8, 2018.
- Dominant language
- R
- Stars
- 66
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
(don't close this; will re-use and update for each release)
- check for existing problems on CRAN checks for ARTool
- double-check CRAN policies
- update R and all packages
-
devtools::install_dev_deps() -
update.packages(ask = FALSE)
-
- bump version and date
- in DESCRIPTION
- in NEWS
-
devtools::check(remote = TRUE, manual = TRUE, run_dont_test = TRUE) - update NEWS
-
spelling::spell_check_package() -
devtools::document() -
devtools::install() -
revdepcheck::revdep_check(num_workers = 4) - rebuild README
-
devtools::check(remote = TRUE, manual = TRUE, run_dont_test = TRUE)- on windows-release (local)
- on whatever is on Github
-
devtools::check_win_release() -
devtools::check_win_devel() - write
cran-comments.md -
devtools::release()
After package goes live on CRAN:
- merge
devontomasterandcran - tag release
- double check zenodo entry
- Matthew Kay
- Lisa A. Elkin
- James J. Higgins
- Jacob O. Wobbrock
- revdepcheck::revdep_reset()
-
usethis::use_dev_version()on dev branch
Template loosely based on https://github.com/r-lib/usethis/issues/338
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.