Skip to content

docs(cran-prep): switch maintainer to Vincent + rewrite cran-comments.md for 0.3.0#111

Open
VincentGuyader wants to merge 3 commits intomasterfrom
docs/cran-prep-0.3.0
Open

docs(cran-prep): switch maintainer to Vincent + rewrite cran-comments.md for 0.3.0#111
VincentGuyader wants to merge 3 commits intomasterfrom
docs/cran-prep-0.3.0

Conversation

@VincentGuyader
Copy link
Copy Markdown
Member

Summary

Two coordinated edits ahead of the CRAN 0.3.0 submission:

  1. DESCRIPTION: swap the cre role from Colin Fay (contact@colinfay.me) to Vincent Guyader (vincent@thinkr.fr). Both remain aut. Vincent pilots the 0.3.0 release. CRAN's submission system will emit a "New maintainer" note and ask the previous maintainer to confirm via email.

  2. cran-comments.md: replace the previous-release boilerplate (download.file feedback) with the actual 0.3.0 release notes:

    • Test environments (local + GHA + win-builder placeholder, filled in once check_win_devel() returns)
    • Maintainer change context
    • Major changes since 0.2.6 grouped as Breaking changes / New features / Security hardening / Bug fixes
    • Reverse-deps note (golem unaffected by the vendored renv removal)
    • Coverage note (99.84%, single uncovered line is a defensive stop() guard)

Local verification

R CMD check --as-cran : 0 errors / 0 warnings / 1 note
note: "unable to verify current time" (transient host glitch, unrelated to package)

The "New maintainer" note is not emitted by local check. CRAN's submission system raises it; that is expected and is the whole point of this PR.

Test plan

  • DESCRIPTION authors order preserved (Fay, Guyader, Parry, Rochette).
  • Only cre role swapped; both Fay and Guyader carry aut.
  • cran-comments.md mentions every breaking change in NEWS.md 0.3.0.
  • cran-comments.md flags the maintainer change explicitly.
  • R CMD check --as-cran clean (0/0/1 transient).
  • After merge: run devtools::check_win_devel() from master, paste win-builder summary into cran-comments.md as a follow-up.
  • After merge: urlchecker::url_check() on master HEAD.
  • After merge: revdepcheck::revdep_check() to confirm golem unaffected.

….md for 0.3.0

Two coordinated edits ahead of the CRAN submission:

1. DESCRIPTION: swap the `cre` role from Colin Fay
   (`contact@colinfay.me`) to Vincent Guyader
   (`vincent@thinkr.fr`). Both remain listed as `aut`. Vincent
   pilots the 0.3.0 release; the maintainer change is
   coordinated between the two authors. CRAN's submission
   system will emit a "New maintainer" note and require email
   confirmation from the previous maintainer.

2. cran-comments.md: replace the previous-release boilerplate
   (CRAN feedback on `download.file()` graceful failure) with
   the actual 0.3.0 release notes:
   - Test environments (local + GHA + win-builder placeholder)
   - Maintainer change context
   - Major changes since 0.2.6 grouped as Breaking changes /
     New features / Security hardening / Bug fixes
   - Reverse-deps note (golem unaffected by vendored renv removal)
   - Coverage note (99.84%, single defensive guard uncovered)

R CMD check --as-cran: 0 errors / 0 warnings / 1 note
("unable to verify current time" host glitch, unrelated).
devtools::test(): no behavioural change (no R/, NAMESPACE, Rd
or test impact in this commit).
Three changes from the pr-reviewer pass:

1. Test environments: replace the literal `TODO` placeholder for
   `check_win_devel()` with explicit "submitted in parallel; the
   result will follow by email" phrasing. Submitting a file with
   `TODO` reads as an unfinished checklist and risks an immediate
   bounce from the CRAN review queue.
2. Maintainer change: spell out the email-confirmation protocol
   explicitly ("the previous maintainer ... will confirm by
   replying to the automated email from CRAN's submission
   system"), instead of relying on the vaguer "coordinated
   between the two authors" phrasing. Makes clear we know the
   handover is gated on Colin's reply, not on internal
   coordination.
3. R CMD check results: keep `0/0/0` as the canonical result but
   add a one-line caveat about the transient "unable to verify
   current time" host-clock NOTE so a CRAN reviewer is not
   surprised if win-builder surfaces it.
@VincentGuyader
Copy link
Copy Markdown
Member Author

/copilot review

… manual verification

revdepcheck::revdep_check() was attempted but its install phase
on the local host stalled on Bioconductor / heavy-stats deps
(ade4, Biobase, ape) pulled in by {AbSolution}. Rather than
keep an unverified claim in cran-comments.md, replace it with
the manual verification that does answer the relevant question:
the only breaking *symbol* removal in 0.3.0 is
`dockerfiler::renv`, and a GitHub-wide code search returns zero
references to it outside `ThinkR-open/dockerfiler` (our own
NEWS) and `cran/dockerfiler` (the 0.2.7 mirror). Combined with
the explicit local grep of {golem}, this shows none of the 3
declared revdeps (golem, AbSolution, shiny2docker) consume the
removed symbol. Default-value flips (FROM, repos, user) are
behavioural and preserve call-site compatibility.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant