You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: MAINTAINERS.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,18 +16,18 @@ A PR can only be merged into master by a maintainer, if all of these conditions
16
16
17
17
Maintainers need to perform the following actions **in the order described here** to push out a release.
18
18
19
-
### Prepare a CRAN submission with `rhub`
19
+
### Preparing a CRAN submission with `rhub`
20
20
21
-
Before starting a release, verify that the result of `rhub` package is stored in [cran-comments.md](cran-comments.md) (the recent result is on top of the file, and the oldest on the bottom).
22
-
If not, you need to do the next steps.
21
+
Before starting a release, check that the output of `rhub` package is stored in [cran-comments.md](cran-comments.md) (the recent output is at the top of the file, and the oldest at the bottom).
22
+
If this is not the case, you must perform the following steps.
23
23
24
24
#### First installation
25
25
```R
26
26
install.packages("rhub")
27
27
library(rhub)
28
28
```
29
29
30
-
For the email address of the maintainer (described on[DESCRIPTION](DESCRIPTION)), `rhub` will ask you to generate a token (on the first check), or you can [reuse one](https://r-hub.github.io/rhub/reference/validate_email.html).
30
+
For the email address of the maintainer (described in[DESCRIPTION](DESCRIPTION)), `rhub` will prompt you to generate a token (on the first check), or you can [reuse one](https://r-hub.github.io/rhub/reference/validate_email.html).
31
31
32
32
#### Check
33
33
Follow this procedure: https://r-hub.github.io/rhub/articles/rhub.html#prepare-a-cran-submission.
@@ -36,8 +36,8 @@ Follow this procedure: https://r-hub.github.io/rhub/articles/rhub.html#prepare-a
36
36
cran_prep<- check_for_cran()
37
37
```
38
38
39
-
⚠️ In local, you can only see one environment execution.
40
-
To see the other, you can get the URLs from the top of the local execution, and open it on a browser.
39
+
⚠️ Locally, you can only see one run of the environment.
40
+
To see the other one, you can get the URLs from the top of the local run, and open it on a browser.
This is a <resubmission | new submission>. In this version, we have:
56
+
This is a <re-submission | new submission>. In this version, we have:
57
57
58
58
* <NEW CHANGE>
59
59
@@ -63,21 +63,21 @@ This is a <resubmission | new submission>. In this version, we have:
63
63
## R CMD check results
64
64
<RESULT OF check_for_cran()>
65
65
66
-
## Reply from CRAN for the last submission
66
+
## Response to CRAN for last submission
67
67
68
68
> <CITATION>
69
69
```
70
-
- Choose if it is a `resubmission` or a `new submission`.
71
-
- Add the new change of this release.
72
-
- Copy-paste the result of the following command, after receiving the emails for all environments on the [email address](DESCRIPTION) of the maintainer from `check_for_cran()`:
70
+
- Choose if this is a `re-submission` or a `new submission`.
71
+
- Add the new change of this version.
72
+
- Copy and paste the output of the following command, after receiving the emails for all environments on the maintainer's [email address](DESCRIPTION) from `check_for_cran()`:
73
73
```R
74
74
cran_prep$cran_summary()
75
75
```
76
76
- Remove all `Version contains large components (X.Y.Z.9000)"`
77
-
- If it is a `resubmission`, copy-paste the result for the last CRAN submission, and reply to false NOTES.
78
-
If not, remove the part:
77
+
- If this is a `re-submission`, copy and paste the result for the last CRAN submission, and answer to false NOTES.
0 commit comments