Release c14 0.2.0
- Dominant language
- R
- Stars
- 10
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
First release:
* [x] `usethis::use_cran_comments()`
* [x] Update (aspirational) install instructions in README
* [x] Proofread `Title:` and `Description:`
* [x] Check that all exported functions have `@return` and `@examples`
* [x] Check that `Authors@R:` includes a copyright holder (role 'cph')
* [x] Check [licensing of included files](https://r-pkgs.org/license.html#sec-code-you-bundle)
* [x] Review
Prepare for release:
* [x] `git pull`
* [x] [Close v0.2.0 milestone](../milestone/1)
* [x] `urlchecker::url_check()`
* [x] `devtools::build_readme()`
* [x] `devtools::check(remote = TRUE, manual = TRUE)`
* [x] `devtools::check_win_devel()`
* [x] `git push`
* [ ] Draft blog post
Submit to CRAN:
* [x] `usethis::use_version('minor')`
* [x] `devtools::submit_cran()`
* [x] Approve email
Wait for CRAN...
* [ ] Accepted :tada:
* [ ] Finish & publish blog post
* [ ] Add link to blog post in pkgdown news menu
* [ ] `usethis::use_github_release()`
* [ ] `usethis::use_dev_version(push = TRUE)`
* [ ] Share on social media
* [ ] (Re)add to https://github.com/benmarwick/ctv-archaeology/issues/71
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the remaining unchecked items in this release checklist, especially the draft and published blog post, the pkgdown news link, and the GitHub release and development-version commands. Start by checking the CRAN submission status and existing README or news content; done means the release is accepted, the announcement is published, and the listed follow-up links and release metadata are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100