<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>FYI </div><div><br></div><div>Some of the points (eg API) are highly relevant to us as far as I can see<br><br><div>
----------------------</div>Yurii Aulchenko <div>(sent from mobile device)</div></div><div><br>Begin forwarded message:<br><br></div><blockquote type="cite"><div><b>From:</b> Kurt Hornik <<a href="mailto:Kurt.Hornik@wu.ac.at">Kurt.Hornik@wu.ac.at</a>><br>
<b>Date:</b> December 11, 2013 at 12:26:34 GMT+1<br><b>To:</b> Kurt Hornik <<a href="mailto:Kurt.Hornik@wu.ac.at">Kurt.Hornik@wu.ac.at</a>><br><b>Cc:</b> Brian Ripley <<a href="mailto:ripley@stats.ox.ac.uk">ripley@stats.ox.ac.uk</a>>, Uwe Ligges <<a href="mailto:uwe.ligges@tu-dortmund.de">uwe.ligges@tu-dortmund.de</a>><br>
<b>Subject:</b> <b>CRAN package maintainer check</b><br><b>Reply-To:</b> <a href="mailto:Kurt.Hornik@wu.ac.at">Kurt.Hornik@wu.ac.at</a><br><br></div></blockquote><blockquote type="cite"><div><span></span><br><span>Dear CRAN package maintainer,</span><br>
<span></span><br><span>We email all CRAN maintainers periodically to check that the email </span><br><span>address is still active and to remind them of the CRAN policies at </span><br><span><<a href="http://CRAN.R-project.org/web/packages/policies.html">http://CRAN.R-project.org/web/packages/policies.html</a>>.</span><br>
<span></span><br><span>Changes to those policies in the last 4 months are given below.</span><br><span></span><br><span>Please check whether your maintainer address needs updating (in</span><br><span>particular in case you moved, or received multiple copies of this</span><br>
<span>message).</span><br><span></span><br><span>Best,</span><br><span>-k</span><br><span></span><br><span>***********************************************************************</span><br><span></span><br><span>Index: CRAN_policies.texi</span><br>
<span>===================================================================</span><br><span>--- CRAN_policies.texi (revision 2906)</span><br><span>+++ CRAN_policies.texi (working copy)</span><br><span>@@ -236,15 +236,23 @@</span><br>
<span> into which they are loaded.</span><br><span></span><br><span> @item</span><br><span>-@acronym{CRAN} packages should use only the public API. Hence they should</span><br><span>-not use entry points not declared as API in installed headers nor</span><br>
<span>-@code{.Internal()} nor @code{.Call()} etc calls to base packages. Such</span><br><span>-usages can cause packages to break at any time, even in patched versions</span><br><span>-of R.</span><br><span>+@acronym{CRAN} packages should use only the public API. Hence they</span><br>
<span>+should not use entry points not declared as API in installed headers nor</span><br><span>+@code{.Internal()} nor @code{.Call()} etc calls to base packages. Also,</span><br><span>+@code{:::} should not be used to access undocumented/internal functions</span><br>
<span>+in base packages. Such usages can cause packages to break at any time,</span><br><span>+even in patched versions of R.</span><br><span></span><br><span>+@end itemize</span><br><span></span><br><span>+@item</span><br>
<span>+Changes to @acronym{CRAN} packages causing significant disruption to</span><br><span>+other packages must be agreed with the @acronym{CRAN} maintainers well</span><br><span>+in advance of any publicity. Introduction of new packages providing</span><br>
<span>+back-compatibility versions of already available packages is not</span><br><span>+allowed.</span><br><span>+</span><br><span> @end itemize</span><br><span>-@end itemize</span><br><span></span><br><span> @node Binary packages, Submission, Source packages, Top</span><br>
<span> @unnumbered Binary packages</span><br><span>@@ -280,12 +288,16 @@</span><br><span> @node Submission, , Binary packages, Top</span><br><span> @unnumbered Submission</span><br><span></span><br><span>-When submitting a package to CRAN you should either</span><br>
<span>+When submitting a package to CRAN you should @strong{either}</span><br><span> @itemize</span><br><span></span><br><span> @item</span><br><span>-use the submission form at @uref{<a href="http://CRAN.R-project.org/submit.html">http://CRAN.R-project.org/submit.html</a>}, or</span><br>
<span>+use the submission form at @uref{<a href="http://CRAN.R-project.org/submit.html">http://CRAN.R-project.org/submit.html</a>}</span><br><span>+(and not send an email). You will be sent a confirmation email which</span><br>
<span>+needs to be accepted.</span><br><span></span><br><span>+@strong{or}</span><br><span>+</span><br><span> @item</span><br><span> upload by anonymous @command{ftp} to</span><br><span> @uref{<a href="ftp://CRAN.R-project.org/@/incoming/">ftp://CRAN.R-project.org/@/incoming/</a>} and send a (plain text ASCII)</span><br>
<span>@@ -293,29 +305,28 @@</span><br><span></span><br><span> @end itemize</span><br><span></span><br><span>+In either case, you can check that the submission was received by</span><br><span>+looking at @uref{<a href="ftp://cran.r-project.org/incoming/">ftp://cran.r-project.org/incoming/</a>}.</span><br>
<span>+</span><br><span> In more detail:</span><br><span></span><br><span> @itemize</span><br><span></span><br><span> @item</span><br><span>-Uploads must be source tarballs as created by @command{R CMD build} and</span><br>
<span>-follow the @file{@var{PACKAGE}_@var{VERSION}.tar.gz} naming scheme.</span><br><span>+Uploads must be source tarballs created by @command{R CMD build} and</span><br><span>+following the @file{@var{PACKAGE}_@var{VERSION}.tar.gz} naming scheme.</span><br>
<span></span><br><span> @item</span><br><span> Please ensure that @command{R CMD check --as-cran} has been run @emph{on</span><br><span> the tarball to be uploaded} before submission. This should be done with</span><br><span>-the current release of R or (preferably) R-devel or R-patched. As</span><br>
<span>-``Writing R Extensions'' used to say</span><br><span>+the current version of R-devel (or if that is not possible, current</span><br><span>+R-patched or the current release of R.) </span><br><span></span><br>
<span>-@quotation</span><br><span>-Please ensure that you can run through the complete procedure with only</span><br><span>-warnings that you understand and have reasons not to eliminate. In</span><br><span>-principle, packages must pass @code{R CMD check} without warnings or</span><br>
<span>+In principle, packages must pass @code{R CMD check} without warnings or</span><br><span> significant notes to be admitted to the main @acronym{CRAN} package</span><br><span> area. If there are warnings or notes you cannot eliminate (for example</span><br>
<span> because you believe them to be spurious) send an explanatory note as</span><br><span>-part of your covering email.</span><br><span>-@end quotation</span><br><span>+part of your covering email, or as a comment on the submission form.</span><br>
<span></span><br><span> @item</span><br><span> For a package update, please check that any packages depending on this</span><br><span>@@ -325,17 +336,18 @@</span><br><span> for the package.</span><br><span></span><br><span> @item</span><br>
<span>-A submission upload should be accompanied by an email to</span><br><span>-@email{CRAN@@<a href="http://R-project.org">R-project.org</a>} sent from the maintainer</span><br><span>-address listed in the package, and using the subject line </span><br>
<span>-`CRAN submission @var{PACKAGE} @var{VERSION}', where @var{PACKAGE} and</span><br><span>-@var{VERSION} are the package name and version, respectively. Plain</span><br><span>-text ASCII emails should be used if at all possible.</span><br>
<span>+An @command{ftp} upload should be accompanied by an email to</span><br><span>+@email{CRAN@@<a href="http://R-project.org">R-project.org</a>} sent from the maintainer address listed in</span><br><span>+the package, and using the subject line `CRAN submission @var{PACKAGE}</span><br>
<span>+@var{VERSION}', where @var{PACKAGE} and @var{VERSION} are the package</span><br><span>+name and version, respectively. Plain text ASCII emails should be used</span><br><span>+if at all possible.</span><br><span></span><br>
<span> If for some reason the submission has to be made by someone else (for</span><br><span> example, a co-author) this needs to be explained, and the designated</span><br><span> maintainer will need to confirm the submission. Explain any change in</span><br>
<span>-the maintainer's email address.</span><br><span>+the maintainer's email address and if possible send confirmation from</span><br><span>+the previous address.</span><br><span></span><br><span> For a new submission, confirm in your email that you have read and agree</span><br>
<span> to these policies. (This includes new versions of previously archived</span><br><span>@@ -343,7 +355,7 @@</span><br><span></span><br><span> If the package needs special treatment (for example if vignettes can</span><br>
<span> only be run or re-built on the maintainer's machine or take a very long</span><br><span>-time), say so in the submission email.</span><br><span>+time), say so in the submission email or on the submission form.</span><br>
<span></span><br><span> Do not email the package itself.</span><br><span></span><br><span>@@ -373,6 +385,12 @@</span><br><span> writing portable packages in @url{../../doc/manuals/R-exts.html,</span><br><span> ``Writing R Extensions''}.</span><br>
<span></span><br><span>+Before submitting a package update, consult the CRAN check page at</span><br><span>+@uref{<a href="http://cran.r-project.org/web/checks/check_results_NAME.html">http://cran.r-project.org/web/checks/check_results_NAME.html</a>},</span><br>
<span>+substituting NAME by the name of your package. In particular, wait for</span><br><span>+that page to be fully updated after publication of a version (which can</span><br><span>+take at least 48 hours) before submitting any corrections.</span><br>
<span>+</span><br><span> @item</span><br><span> If an update will change the package's API and hence affect packages</span><br><span> depending on it, it is expected that you will contact the maintainers of</span><br>
</div></blockquote></body></html>