Release rticles 0.28
Open
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 1.5k
- Forks
- 517
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
Prepare for release:
-
git pull - Check current CRAN check results
- Check if any deprecation processes should be advanced, as described in Gradual deprecation
- Polish NEWS
-
urlchecker::url_check() -
devtools::build_readme() -
devtools::check(remote = TRUE, manual = TRUE) -
devtools::check_win_devel() -
revdepcheck::cloud_check() - Update
cran-comments.md -
git push - Draft blog post
- Slack link to draft blog in #open-source-comms
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
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 with the unchecked release checklist in this issue, especially the draft blog post and the pkgdown news-menu link. Confirm the CRAN submission status, then finish and publish the blog post, add its link, create the GitHub release, and complete the listed sharing steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- content, documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100