Release btw 1.3.0
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 137
- Forks
- 10
- Avg merge
- 10h 48m
- Merged PRs (30d)
- 4
Description
Prepare for release:
-
git pull - Check current CRAN check results
- Advance deprecations, if needed
- Polish NEWS
-
urlchecker::url_check() -
devtools::build_readme() -
devtools::check(remote = TRUE, manual = TRUE) -
devtools::check_win_devel() - Update
cran-comments.md -
git push - Draft blog post
Submit to CRAN:
-
usethis::use_version('minor') -
devtools::submit_cran() - Approve email
Wait for CRAN...
- Accepted 🎉
- 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
- Slack link to blog post, bluesky, and linkedin in #open-source-comms
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
Start by reviewing the completed release checklist and the remaining blog-post tasks. Draft and publish the blog post, add its link to the pkgdown news menu, run the listed usethis release commands, and complete the stated social-media sharing steps; the release is done when all unchecked items are complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, r
- Domain
- content, documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100