posit-dev / posit-dev/mcptools
Release mcptools 1.0.0
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 196
- Forks
- 21
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
Prepare for release:
-
git pull - Check current CRAN check results
- 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
Submit to CRAN:
-
usethis::use_version('major') -
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
No contributing guide indexed for this repository
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 steps in the issue, especially devtools::check_win_devel(), usethis::use_version('major'), and devtools::submit_cran(). Review cran-comments.md and the drafted blog post before submitting; done means CRAN accepts the package, the blog post and pkgdown news link are published, 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
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100