CRAN Repository Policy

Version $Revision: 5321 $
CRAN Repository Maintainers

Next: , Previous: , Up: (dir)  

Top


Next: , Previous: , Up: Top  

Preamble

This document describes the policies in place for the R package repository hosted by the Comprehensive R Archive Network. In what follows, this CRAN package repository will be referred to as “CRAN”.

CRAN is maintained by the efforts of volunteers (the “CRAN team”) and the resources of the R Foundation and the employers of those volunteers (WU Wien, TU Dortmund, U Oxford, U Auckland). Having a package distributed by CRAN is subject to a set of policies, and submitting a package (including an update) to CRAN indicates agreement to these policies.

CRAN hosts packages of publication quality and is not a development platform. A package’s contribution has to be non-trivial.

Distributing code or documentation is subject to legal requirements, and CRAN operates in many jurisdictions. One of the aims of these policies is to ensure that the distributors meet their legal obligations of diligence without excessive work.

The time of the volunteers is CRAN’s most precious resource, and they reserve the right to remove or modify packages on CRAN without notice or explanation (although notification will usually be given).

All correspondence with CRAN must be sent to CRAN-submissions@R-project.org (for submissions) or CRAN@R-project.org (for published packages) and not to members of the team, in plain text ASCII and not HTML.


Next: , Previous: , Up: Top  

Source packages


Next: , Previous: , Up: Top  

Binary packages

Policies for when a (Windows or macOS) binary package will be distributed:

Binary packages are not accepted from maintainers: CRAN will only host binary packages prepared by those responsible for the binary areas. Their packages are made automatically by batch jobs and can take a day or two to appear on the CRAN master site (maybe longer to reach CRAN mirrors).

Binary packages are built for the current version of R: they may also be built for the last version in the previous series (e.g. R 3.1.3 when R 3.2.x is current) or for R-devel.

Questions about binary packages should be addressed to those responsible for building them: Simon Urbanek (macOS) and Uwe Ligges (Windows); email addresses ‘First.Lastname@R-project.org’.


Next: , Previous: , Up: Top  

Submission

When submitting a package to CRAN you should use the submission form at https://CRAN.R-project.org/submit.html (and not send an email). You will be sent a confirmation email which needs to be accepted.

You can check that the submission was received by looking at https://CRAN.R-project.org/incoming/. Submission difficulties (such as non-receipt of the confirmation email) can be discussed with cran-sysadmin@R-project.org.

In more detail:


Previous: , Up: Top  

Re-submission

Re-submission is done in the same way as submission, using the ‘Optional comment’ field on the web form (and not a separate email) to explain how the feedback on previous submission(s) has been addressed.

Updates to previously-published packages must have an increased version. Increasing the version number at each submission reduces confusion so is preferred even when a previous submission was not accepted.

For packages which have been archived since February 2018, a snapshot of the CRAN results page at the time of archival will be available under https://cran-archive.r-project.org/web/checks/. (Note that only a few of the links from the snapshot will work: normally those to listed ‘Additional issues’ will.)

A package showing issues for macos-arm64 or an ‘M1mac’ additional issue should be checked using the macbuilder service prior to re-submission.