Release Version V0.2.6
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 31
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Release new version related to the maintainer update:
First release
- Proof read
Title:andDescription:and ensure they are informative - Check that all exported functions have
@returnand@examples - Check that
Authors@R:includes a copyright holder (role 'cph') - Review extrachecks
-
usethis::use_cran_comments()(optional)
Prepare for release
- Check current CRAN check results
- Check licensing of included files
- Review pkgdown reference index for, e.g., missing topics
- Bump version
- Update
cran-comments.md(optional) - Update NEWS.md
- Review pkgdown website
-
urlchecker::url_check() - Check with local machine
- Check with GitHub Actions
- Check with win-builder
Submit to CRAN
- Draft GitHub release
- Submit to CRAN via web form
- Approve emails
Wait for CRAN
- Accepted 🎉
- Post on r-packages mailing list
- Tweet
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 release checklist in this issue, then inspect NEWS.md, cran-comments.md, the pkgdown reference index, and the current CRAN check results. Review the package metadata and version before running the listed URL, local, GitHub Actions, and win-builder checks; done means the release is submitted to CRAN and the acceptance follow-up is completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, r
- Domain
- ci-cd, documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100