Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address NOTE on large version components (issue #1028) #1030

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Address NOTE on large version components (issue #1028) #1030

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions release.Rmd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -235,6 +235,17 @@ This is meant to be a last-minute, final reminder to double-check that all is st
Checking with r-devel is required by CRAN policy and it will be done as part of CRAN's incoming checks.
There is no point in skipping this step and hoping for the best.

When you are preparing to upload a package with a development version (such as in the case when you update a previously released package), both of these will generate at least one `NOTE`:

```
❯ checking CRAN incoming feasibility ... [5s/35s] NOTE
Maintainer: ‘Hadley Wickham <[email protected]>’

Version contains large components (1.2.0.9000)
```

This `NOTE` will be eliminated when you bump the version number (@sec-release-process) so there is no specific action necessary at this time.

Note that the brevity of this list implicitly reflects that tidyverse packages are checked after every push via GitHub Actions, across multiple operating systems and versions of R (including the development version), and that most of the tidyverse team develops primarily on macOS.
CRAN expects you to "make all reasonable efforts" to get your package working across all of the major R platforms and packages that don't work on at least two will typically not be accepted.

Expand Down