|
| 1 | +# pcatR 1.0.1 CRAN submission record |
| 2 | + |
| 3 | +This file tracks the initial CRAN submission separately from the immutable |
| 4 | +GitHub `v1.0.0` release. |
| 5 | + |
| 6 | +## Completed in the source tree |
| 7 | + |
| 8 | +- Package version advanced to 1.0.1. |
| 9 | +- DESCRIPTION cites both source articles by DOI. |
| 10 | +- Source-derived content and adaptations are documented in `LICENSE.note` and |
| 11 | + installed `inst/COPYRIGHTS`. |
| 12 | +- Package citation is generated from DESCRIPTION metadata; both source articles |
| 13 | + have complete author lists. |
| 14 | +- Installed technical guides include PDF and self-contained HTML plus editable |
| 15 | + R Markdown source, CSS, and rendering instructions. |
| 16 | +- Unreleased-version metadata identifies the guide as a CRAN submission |
| 17 | + candidate rather than assigning version 1.0.1 a release date. |
| 18 | +- The documented minimum R version is exercised by an R 4.1 CI job. |
| 19 | + |
| 20 | +## Required evidence before submission |
| 21 | + |
| 22 | +- [x] Local source spelling and URL checks reviewed. |
| 23 | +- [x] `R CMD build` produces exactly `pcatR_1.0.1.tar.gz`. |
| 24 | +- [x] `R CMD check --as-cran pcatR_1.0.1.tar.gz` reviewed with no errors or |
| 25 | + warnings and all notes explained. |
| 26 | +- [x] Archive contents inspected for excluded development and release files. |
| 27 | +- [x] GitHub Actions pass on Windows, macOS, Linux, R devel, release, oldrel, |
| 28 | + and R 4.1. |
| 29 | +- [x] The exact uploaded source archive passes full-manual `--as-cran` checks |
| 30 | + under current R-release and R-devel. |
| 31 | +- [x] A clean local pkgdown build was inspected for its home, reference, |
| 32 | + article, citation, author, license, attribution, and release pages. |
| 33 | +- [x] Joint software copyright ownership is implemented consistently in |
| 34 | + `Authors@R`, `LICENSE`, `LICENSE.md`, and `inst/COPYRIGHTS`. |
| 35 | +- [ ] Retain Lilac Li's written approval of her authorship and copyright-holder |
| 36 | + role, Jae Man Park's maintainer role, the MIT and CC BY 4.0 licensing |
| 37 | + treatment, public distribution, and submission to CRAN. |
| 38 | +- [ ] Win-builder R-devel and R-release results reviewed. |
| 39 | +- [ ] Freeze one final source archive and retain its generated `.sha256` file; |
| 40 | + send those exact archive bytes to Win-builder and CRAN without rebuilding. |
| 41 | +- [ ] Maintainer obtains confirmation of the package name and source-content |
| 42 | + treatment from the original instrument authors before submission. |
| 43 | +- [ ] Maintainer submits only the source archive through CRAN's submission form |
| 44 | + and responds to CRAN's confirmation email. |
| 45 | + |
| 46 | +Registry searches can show that a name is currently unused, but they do not |
| 47 | +reserve it. Recheck CRAN and Bioconductor immediately before submission. |
| 48 | + |
| 49 | +## Pre-freeze automated evidence |
| 50 | + |
| 51 | +Candidate workflows have successfully checked exact uploaded archives under |
| 52 | +current R-release and R-devel with full PDF manuals. The workflow now stores a |
| 53 | +generated `.sha256` file beside each archive and verifies it before both checks. |
| 54 | + |
| 55 | +The final source head, run IDs, and SHA-256 are deliberately pending. Record |
| 56 | +them only after the external approvals are retained, the source is frozen, and |
| 57 | +one exact archive is selected for Win-builder and CRAN submission. |
| 58 | + |
| 59 | +## Registry check recorded July 12, 2026 |
| 60 | + |
| 61 | +- `pcatR` was absent from the current CRAN package index. |
| 62 | +- CRAN's exact `src/contrib/Archive/pcatR/` path returned HTTP 404, indicating |
| 63 | + no historical archive at that exact case-sensitive name. |
| 64 | +- The exact package name was absent from Bioconductor's release package page. |
| 65 | + |
| 66 | +These observations are point-in-time checks, not a reservation or acceptance |
| 67 | +decision. |
0 commit comments