-
Notifications
You must be signed in to change notification settings - Fork 22
Developers
Florian Hartig edited this page Jun 14, 2022
·
2 revisions
I consider the main git branch the development branch, and the CRAN releases the release branch, i.e. I don't have an extra release / dev branch on this repo.
Thus, the usual workflow for a feature should be:
- create feature branch
- implement feature
- update
- create PR, for more complicate issues ask for code review
- merge with main (dev) branch
If a feature branch relates to an issue, I prefer to have the issue number in name of the branch (see existing branches)
To prepare for a CRAN update, check first that all issues associated with this update are closed, and/or decide to push those to the next release.
Then, update version/date info, and make sure there are no issues
- Local checks
- GH Actions, all OS
- https://cran.r-project.org/web/checks/check_results_DHARMa.html
- All R versions on https://win-builder.r-project.org/upload.aspx