An associated problem, for the wish list, is that it would be nice for
package developers to have a way to automatically distinguish between
NOTEs that can usually be ignored (e.g. a package suggests a package
that is not available for cross reference checks - I have several case
where the suggested package depends on the package being built, so this
NOTE occurs all the time), and NOTEs that are really pre-WARNINGS, so
that one can flag these and spend time fixing them before they become a
WARNING or ERROR. Perhaps two different kinds of notes?
(And, BTW, having been responsible for a certain amount of the
>[*] Since answering several emails a day about why their
>results were different was taking up far too much time.
I think --as-cran is great.)
Paul
On 12-03-27 02:19 PM, Uwe Ligges wrote:
On 27.03.2012 19:10, Jeffrey Ryan wrote:
Is there a distinction as to NOTE vs. WARNING that is documented? I've
always assumed (wrongly?) that NOTES weren't an issue with publishing on
CRAN, but that they may change to WARNINGS at some point.
We won't kick packages off CRAN for Notes (but we will if Warnings are
not fixed), but we may not accept new submissions with significant Notes.
Best,
Uwe Ligges
Is the process by which this happens documented somewhere?
Jeff
On 3/27/12 11:09 AM, "Gabor Grothendieck"<ggrothendi...@gmail.com> wrote:
2012/3/27 Uwe Ligges<lig...@statistik.tu-dortmund.de>:
On 27.03.2012 17:09, Gabor Grothendieck wrote:
On Tue, Mar 27, 2012 at 7:52 AM, Prof Brian Ripley
<rip...@stats.ox.ac.uk> wrote:
CRAN has for some time had a policies page at
http://cran.r-project.org/web/packages/policies.html
and we would like to draw this to the attention of package
maintainers.
In
particular, please
- always send a submission email to c...@r-project.org with the
package
name and version on the subject line. Emails sent to individual
members
of
the team will result in delays at best.
- run R CMD check --as-cran on the tarball before you submit it. Do
this with the latest version of R possible: definitely R 2.14.2,
preferably R 2.15.0 RC or a recent R-devel. (Later versions of R are
able to give better diagnostics, e.g. for compiled code and
especially
on Windows. They may also have extra checks for recently uncovered
problems.)
Also, please note that CRAN has a very heavy workload (186 packages
were
published last week) and to remain viable needs package
maintainers to
make
its life as easy as possible.
Regarding the part about "warnings or significant notes" in that page,
its impossible to know which notes are significant and which ones are
not significant except by trial and error.
Right, it needs human inspection to identify false positives. We
believe
most package maintainers are able to see if he or she is hit by such a
false
positive.
The problem is that a note is generated and the note is correct. Its
not a false positive. But that does not tell you whether its
"significant" or not. There is no way to know. One can either try to
remove all notes (which may not be feasible) or just upload it and by
trial and error find out if its accepted or not.
--
Statistics& Software Consulting
GKX Group, GKX Associates Inc.
tel: 1-877-GKX-GROUP
email: ggrothendieck at gmail.com
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
