-
Notifications
You must be signed in to change notification settings - Fork 42
CRAN releases
Parent: Developer
Release checklist
-
Wait a reasonable time after making any changes to the code. Remember that CRAN releases cannot be made in rapid succession. It makes sense to wait a day to let even the most minor improvements to documentation "cool off", a week for small changes to functionality, or a season for significant changes. And be sure to follow the deprecate-defunct-remove procedure.
-
Ensure that a local build/check works cleanly. This ought to be done with every build, but it should still be done again in the final hours before a submission.
-
Ensure that external checks done by the github action are all clean. (Again, this ought to be checked for all pushes of the repository.)
-
Use
devtools::check()to check on a variety of architectures. Many times, these will fail owing to problems on the checking machines, e.g. with failure to installsf(as of 2021 Jan) and so this is a non-blocking step in such circumstances.