make /base/utils (PEcAn.utils ) package CRAN ready

[moki1202]

The primary aim of this issue is to make our package PEcAn.utils, CRAN ready. To achieve this, we would be following strict guidelines and policies set by the CRAN team.

Following are the necessary checkboxes that need to be ticked before we think about releasing the package-

• [ ] R CMD check should not return any warnings, notes and errors. One exception: Since the package has never been on CRAN before, "checking CRAN incoming feasibility" will always return a NOTE stating the maintainer name and the package license.
• [ ] An additional NEWS.md file should be added to each package. It should list all the API changes in each release.
• [ ] It should meet every requirement mentioned by CRAN in this document
• [ ] Any package about to be released to CRAN must not depend on any other NON-CRAN package!
• [ ] Check that the package maintainer is correctly assigned and their email is up to date.
• [ ] Review descriptive text in DESCRIPTION and make sure it clearly describes the purpose of this package (not just PEcAn as a whole).
• [ ] Delete tests/Rcheck_reference.log
• [ ] Bump version and date!
• [ ] no Roxygen example section for un-exported functions.
• [ ] exported functions should have return value documentation.
• [ ] assign cph(copyright holder) role.

[Aariq]

Some additional things in #1681

[github-actions[bot]]

This issue is stale because it has been open 365 days with no activity.