CRAN release workflow
Closed this issue · 7 comments
prepare for release:
- Check CRAN issues (if published)
- urlchecker::url_check()
- devtools::check(document = FALSE)
- rhub::check_for_cran()
- Update cran-comments.md for release
- Update / check NEWS.md
- R CMD check --as-cran (use Build Source Package to create
rsofun_4.4.tar.gzfile) - git push remaining changes
Submit to CRAN:
- Update DESCRIPTION file for Title compliance and specifying package maintainer
- devtools::submit_cran()
- Approve email
- Accepted email
Check Title compliance!
Should be long and descriptive, not repeating the package name or anything close.
The mandatory ‘Title’ field should give a short description of the package. Some package listings may truncate the title to 65 characters. It should use title case (that is, use capitals for the principal words: tools::toTitleCase can help you with this), not use any markup, not have any continuation lines, and not end in a period (unless part of …). Do not repeat the package name: it is often used prefixed by the name. Refer to other packages and external software in single quotes, and to book titles (and similar) in double quotes.
from https://cran.r-project.org/doc/manuals/r-devel/R-exts.html#The-DESCRIPTION-file
The P-model and BiomeE Modelling Framework
would be ok
Or the abbreviation of rsofun:
R Simulating Optimal FUNctioning framework for site-scale simulations of ecosystem processes
?
Beni's suggestion is too long, so I would use The Simulating Optimal FUNctioning framework in R as title and add Implements the P-model and BiomeE modelling framework for site-scale simulations of ecosystem processes, including model calibration. as description.