-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathcran-comments.Rmd
More file actions
66 lines (41 loc) · 1.51 KB
/
cran-comments.Rmd
File metadata and controls
66 lines (41 loc) · 1.51 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
---
title: "cran-comments"
output: github_document
editor_options:
chunk_output_type: console
---
## Reason for update
`dscore 2.0.0` is a major new release that builds on more extensive data
## Resubmission 1
*Why is such a quick update needed? Please explain. Please also re-read the CRAN policies about submission frequency.And why is there a major new release after only 6 days? This is very confusing....*
I realize 6 days is short. Version 1.11.0 was a regular maintenance release and provides a stable fallback for users not yet ready to transition. Version 2.0.0 introduces a new key and changes an important default, which some collaborators need immediately, but may break code for existing users. Having both versions on CRAN ensures continuity for existing users and access to the new functionality.
*Is there some reference about the method you can add in the Description field in the form Authors (year) <doi:10.....>?*
I updated DESCRIPTION with the relevant DOI reference.
## Test environments
### Local
```{r}
R.Version()$version.string
```
## Local check
Package built by
```{r eval = FALSE}
library("devtools")
build()
```
```{bash eval=FALSE}
R CMD CHECK ../dscore_2.0.0.tar.gz
```
Status: OK
## win-builder
```{r eval=FALSE}
devtools::check_win_devel()
```
Upload of the dscore package to win-builder failed.
### RHUB
```{r eval=FALSE}
rhub::rhub_check()
```
Using three builds: linux, windows, macos.
Status: OK
## Downstream dependencies
There are no downstream dependencies for this package.