Message-ID: <b39e3693-5861-3de2-2b0c-b7ab64eee6aa@gmail.com>
Date: 2019-12-15T20:35:16Z
From: Duncan Murdoch
Subject: [R-pkg-devel] Time for CRAN response
In-Reply-To: <000001d5b375$8e1b5880$aa520980$@gmail.com>
On 15/12/2019 1:29 p.m., Tiago Olivoto wrote:
> Dear all,
>
> I've submitted my package 'metan' to CRAN for the first time a few weeks ago
> and received some suggestions to improve the code. After fixing some bugs,
> I've resubmitted it on November 25, but I still don't have any response and
> the package was not found in incoming/ dir on CRAN cran ftp site. Since it
> is my first experience, I would like to have an idea about how long the CRAN
> team usually decides about a package submission.
>
If it is not in incoming/, something went wrong. The most common thing
to go wrong is that the maintainer didn't respond to the confirmation
message. That message looks like this for a resubmission. I assume
first time submissions have a similar message:
> Dear Duncan Murdoch
> Someone has submitted the package rgl to CRAN.
> You are receiving this email to confirm the submission as the maintainer of
> this package.
> To confirm the submission to CRAN, follow or copy & paste the following
> link into your browser:
> ...
When you confirm submission, you'll get another message that looks like
this:
> [This was generated from CRAN.R-project.org/submit.html]
>
> The following package was uploaded to CRAN:
> ===========================================
>
> Package Information:
> Package: rgl
> Version: 0.100.26
> ...
After that, it goes into a queue for checking, and usually within a few
days you'll be told about problems with it or it will be accepted to
CRAN. (Sometimes you'll be told very quickly, if the automated checks
find a problem.)
Duncan Murdoch