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
* Corrected the URLs and removed `LazyData` field in the DESCRIPTION file.
* Added a new file `WORDLIST` to allow custom words with `spelling` package.
* Updated the documentation of the maintainers to execute `rhub` package before starting a new release
* Added a new file `cran-comments.md` for the CRAN submission
* Updated the `release` workflow to update the last version in `cran-comments.md`
Description: To visualize the execution data of the processes on BPMN (Business Process Model and Notation) diagrams, using overlays, style customization and interactions, with the bpmn-visualization TypeScript library.
Copy file name to clipboardExpand all lines: MAINTAINERS.md
+67Lines changed: 67 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,73 @@ 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
+
### Preparing a CRAN submission with `rhub`
20
+
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
+
24
+
#### First installation
25
+
```R
26
+
install.packages("rhub")
27
+
library(rhub)
28
+
```
29
+
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
+
32
+
#### Check
33
+
Follow this procedure: https://r-hub.github.io/rhub/articles/rhub.html#prepare-a-cran-submission.
34
+
35
+
```R
36
+
cran_prep<- check_for_cran()
37
+
```
38
+
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 <re-submission | new submission>. In this version, we have:
57
+
58
+
* <NEW CHANGE>
59
+
60
+
## Test environments
61
+
<RESULT OF check_for_cran()>
62
+
63
+
## R CMD check results
64
+
<RESULT OF check_for_cran()>
65
+
66
+
## Response to CRAN for last submission
67
+
68
+
> <CITATION>
69
+
```
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
+
```R
74
+
cran_prep$cran_summary()
75
+
```
76
+
- Remove all `Version contains large components (X.Y.Z.9000)"`
77
+
- If this is a `re-submission`, copy and paste the result for the last CRAN submission, and answer to false NOTES.
78
+
Otherwise, remove the part:
79
+
```mdxjs
80
+
## Response to CRAN for last submission
81
+
82
+
> <CITATION>
83
+
```
84
+
85
+
19
86
### GitHub issues and milestones update
20
87
21
88
**Note:** we always put issues related to a version in a Milestone whose name matches the version.
0 commit comments