Release repo.data 0.2.3
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 3
- Forks
- 1
- Avg merge
- 2h 33m
- Merged PRs (30d)
- 1
Description
Prepare for release:
* [x] `git pull`
* [x] Check [current CRAN check results](https://cran.rstudio.org/web/checks/check_results_repo.data.html)
* [x] [Polish NEWS](https://style.tidyverse.org/news.html#news-release)
* [x] `urlchecker::url_check()`
* [x] `devtools::build_readme()`
* [x] `devtools::check_win_devel()`
* [x] `devtools::check(remote = TRUE, manual = TRUE)`
* [x] Update `cran-comments.md`
* [x] `git push`
Submit to CRAN:
* [x] `usethis::use_version('patch')`
* [x] `devtools::submit_cran()`
* [x] Approve email
Wait for CRAN...
* [ ] Accepted :tada:
* [ ] `usethis::use_github_release()`
* [ ] `usethis::use_dev_version(push = TRUE)`
Contributor guide
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.
Research direction
Follow the checked release checklist in the issue, starting by confirming the CRAN submission status. When CRAN accepts repo.data 0.2.3, run use_github_release(), then use_dev_version(push = TRUE). Done means the GitHub release is created and the development version is pushed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100