Process for testing "devel" and "pre release" versions before their upload on CRAN

Intro and justification

To avoid uploading to CRAN versions of the package with various errors and bugs, it is very important that we test thoroughly the package during its development stage but, more importantly, during its pre-release stage.

For the testers

To streamline this process, at certain points a source package will be created and uploaded to an agreed-upon Google Drive folder, from where it can be installed in a test or production environment. During the development stage, this package will be named AdhereR-devel to avoid any conflicts with the stable release that may be installed on the system, but during the (hopefully very short) pre-release stage, the package is named AdhereR and overrides the stable release (this is because we want to also test any potential issues due to naming).

For the package creator(s)

To automatically create the source package and upload it to the Google Drive, run in an R console/RStudio (in the Project Root Path):

devtools::document(roclets=c('rd', 'collate', 'namespace', 'vignette'));
devtools::build(path="~/Google Drive/AdhereR/latest-package-for-testing/", binary=FALSE, vignettes=TRUE, manual=TRUE);

Feedback

We encourage any suggestions/comments to be made using the Issues feature of the GitHub repository.