Release CircE 1.2
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the README, package metadata, exported-function documentation, and the pkgdown news menu referenced in the checklist. Run the listed urlchecker and devtools checks before preparing the CRAN submission. Done means the release checklist is complete, CRAN accepts the package, the blog post and GitHub release are published, and the development version is updated.
Written by the indexing model from the issue text.
Description
First release:
-
usethis::use_news_md() -
usethis::use_cran_comments() - Update (aspirational) install instructions in README
- Proofread
Title:andDescription: - Check that all exported functions have
@returnand@examples - Check that
Authors@R:includes a copyright holder (role 'cph') - Check licensing of included files
- Review https://github.com/DavisVaughan/extrachecks
Prepare for release:
-
git pull -
usethis::use_github_links() -
urlchecker::url_check() -
devtools::check(remote = TRUE, manual = TRUE) -
devtools::check_win_devel() -
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) -
usethis::use_news_md() - Share on social media
- Dominant language
- R
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
Similar issues
-
bug priority: should
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
The-Strategy-Unit/nhp_outputs#477 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Open-Systems-Pharmacology/OSPSuite.ReportingEngine#1380 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Open-Systems-Pharmacology/OSPSuite.ParameterIdentification#335 ·