A lot is automated, but another lot has to be checked manually. It
depends on the package and its notes.
Then policies you are quoting have two reasons:
1. we take a look what is going on if a submission comes in too quickly
as this is typically suspicious. Hence a quick submission creates manual
work in any case,
2. each version of a package is archived, so when people submit
frequently, CRAN is growing quickly.
As CRAN is a repository for releases software, we expect that releases
are well tested and hence do not happen too frequently.
In case you nevertheless found a serious bug, please submit a fixed
version and explain why this was needed in the submission comments.
Best,
Uwe Ligges
On 31.05.2018 18:29, Boxuan Cui wrote:
Hi,
During my recent CRAN submissions, I noticed a more streamlined/automatic
process. I am wondering if the submission still requires a manual approval,
or does it go to CRAN automatically after all checks?
I am asking because I accidentally shipped a showstopper bug for a new
feature for DataExplorer v0.6
<https://CRAN.R-project.org/package=DataExplorer> yesterday. The fix is one
line of code change.
However, I am certainly aware of the CRAN Repository Policy
<https://cran.r-project.org/web/packages/policies.html#Submission> and
definitely respect that:
*Submitting updates should be done responsibly and with respect for the
volunteers’ time. Once a package is established (which may take several
rounds), “no more than every 1–2 months” seems appropriate.*
If this is the case, I will wait for another month or two to push a fix to
CRAN, and push the fixed version to GitHub for now.
Thank you!
Best,
Boxuan (Bo)
[[alternative HTML version deleted]]
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
