Release afc 1.5.0
- Dominant language
- R
- Stars
- 0
- Forks
- 0
- Avg merge
- 4h 38m
- Merged PRs (30d)
- 5
Description
Prepare for release:
* [x] `git pull`
* [x] Check [current CRAN check results](https://cran.rstudio.org/web/checks/check_results_afc.html)
* [x] [Polish NEWS](https://style.tidyverse.org/news.html#news-release)
* [x] `usethis::use_github_links()`
* [x] `urlchecker::url_check()`
* [x] `devtools::build_readme()`
* [x] `devtools::check(remote = TRUE, manual = TRUE)`
* [x] `devtools::check_win_devel()`
* [x] Update `cran-comments.md`
* [x] `git push`
* [x] 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
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by checking the current CRAN status for afc 1.5.0 and the remaining unchecked release steps. Finish and publish the blog post, add its link to the pkgdown news menu, create the GitHub release, update the development version, and share the release. Done means CRAN has accepted the package and every checklist item is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100