[Epic F] CRAN Release v0.2.0

[chris-prener]

Objective

Prepare and submit deprivateR v0.2.0 to CRAN, resolving all pre-submission check findings.

Child issues

• Prepare release documentation: README.md, NEWS.md, and cran-comments.md #80 — Prepare release documentation: README.md, NEWS.md, and cran-comments.md
• Finalize package version number in DESCRIPTION for release #81 — Finalize package version number in DESCRIPTION for release
• Run pre-release win-builder and R-hub checks #82 — Run pre-release win-builder and R-hub checks
• Fix invalid DOI URL in README (404) #83 — Fix invalid DOI URL in README (404)
• Fix maintainer email case mismatch for CRAN submission #84 — Fix maintainer email case mismatch for CRAN submission
• Sync index.md with README updates #86 — Sync index.md with README updates

Acceptance criteria

• All child issues closed
• Win-builder and R-hub checks pass with 0 ERRORs, 0 WARNINGs, 0 NOTEs
• Package submitted to CRAN via devtools::submit_cran()

Dependencies

None.

Notes

Issues #83 and #84 were surfaced by the win-builder check run in #82. Sequence: fix #84 and #83 first (blockers), then finalize docs (#80), version (#81), re-run checks (#82), and submit.

[chris-prener]

Epic Retrospective

Outcome

All child issues resolved in a single branch/PR (#87). The package is now prepared for CRAN submission pending final win-builder/R-hub confirmation (#82).

What was delivered

Issue	Summary
#84	Maintainer email casing fixed
#83	Invalid DOI badge removed
#81	Version set to 0.2.0
#80	NEWS.md, README, cran-comments.md updated
#86	index.md created as pkgdown homepage

What went well

• Batching all issues into one branch was efficient — the changes were tightly coupled and benefited from a single pass
• No functional code changes meant low risk and fast review
• Spelling CI caught new words early

What could be improved

• Could have anticipated the WORDLIST issue before pushing (check spelling::spell_check_package() locally)
• The epic originally missed Sync index.md with README updates #86 (index.md sync) — was added mid-flight

Remaining work

• Run pre-release win-builder and R-hub checks #82 — Re-run win-builder and R-hub checks to confirm clean results
• Submit to CRAN via devtools::submit_cran()

[chris-prener]

Epic Retrospective

Epic: [Epic F] CRAN Release v0.2.0 (#85)
Closed: 2026-05-31
Milestone: v0.2.0

What shipped

• Prepared release documentation: README.md, NEWS.md, and cran-comments.md (Prepare release documentation: README.md, NEWS.md, and cran-comments.md #80)
• Finalized package version in DESCRIPTION (Finalize package version number in DESCRIPTION for release #81)
• Ran win-builder and R-hub pre-release checks — 0 ERRORs, 0 WARNINGs, 0 NOTEs (Run pre-release win-builder and R-hub checks #82)
• Fixed invalid DOI URL in README that returned 404 (Fix invalid DOI URL in README (404) #83)
• Fixed maintainer email case mismatch blocking CRAN submission (Fix maintainer email case mismatch for CRAN submission #84)
• Synced index.md (pkgdown landing page) with README updates (Sync index.md with README updates #86)
• Package submitted to CRAN via devtools::submit_cran()

Descoped or deferred

None.

Architectural decisions

• No ADRs filed. The epic was execution-focused (checklist-driven release prep) with no structural decisions required.

KR impact

No supporting objective.

Lessons

• Win-builder checks surfaced two blockers (Fix invalid DOI URL in README (404) #83, Fix maintainer email case mismatch for CRAN submission #84) that weren't caught locally — running external checks early in a release cycle is essential.
• Maintaining index.md separately from README creates sync drift; a future automation or single-source approach would reduce manual bookkeeping.
• The release prep sequence (fix blockers → finalize docs → re-check → submit) worked well as a structured workflow.

Follow-on epics

None.