Release 1.1: Common tasks, Dev acknowledgement, versioning, helper packages/websites, etc

[manciniedoardo]

Master PR

Common Release Tasks

All of these small Release Tasks should be done in one issue and not split out across multiple issues and PRs. I have created a common task list for us to check and hope to develop the task (if needed) below. If we can standardized this stuff, then we could build a release_function that is a wrapper around the https://usethis.r-lib.org/reference/use_release_issue.html

Prepare for release:

• New devs to description File and old devs to acknowledgements
• Review FAQs
• Review Cheatsheet
• Polish news
• Update README schedule for future releases
• Check current CRAN check results
• Scan and remove non-ascii characters - Remove non-ascii characers #2456
• Check if any deprecation processes should be advanced, as described in Gradual deprecation
• urlchecker::url_check()
• devtools::check(remote = TRUE, manual = TRUE)
• devtools::check_win_devel() - doesn't work with Remtoes
• rhub::check_for_cran()
• revdepcheck::revdep_check(num_workers = 4)
  • Looks to be deprecated and not recommended anymore
• Draft blog post

Submit to CRAN:

• Be sure to use [skip vbump] in PR Title to prevent upversioning
• usethis::use_version('major')
• devtools::submit_cran()
• Approve email
• Monitor submission form here: https://r-hub.github.io/cransays/articles/dashboard.html

CRAN Accepted:

• usethis::use_github_release()
• usethis::use_dev_version()
• Finish blog post
• Add Releases and tar.gz file to the Release
• Review admiraldiscovery (presentations and find a function)
• Add link to blog post in pkgdown news menu (?)
• Push forward deprecation

Loose Guidance for particular tasks

New presentations

• Open Source: The Current State of the Industry and Projections for the Future (Keynote) - Ross Farrugia, Michael Rimler ​
• From Stowaway to Admiral, a R-iveting Tale of a Hierarchical Composite Endpoint’s Journey from Idea to Dataset – Nicole Major Slides, Paper​
• Population Pharmacokinetic Analysis Data (ADPPK) Programming in {admiral} and the pharmaverse – Jeff Dickinson Poster, Paper​
• {admiral} - from open source through to company implementation - Ross Farrugia Slides, Paper
• Bridging the Gap Between the pharmaverse and Company Internal Resources – Kangjie Zhang Slides, Paper

For the two below, may have to wait until next update as presentations are yet to be given

• Two hats, one noggin: Perspectives on working as a developer and as a user of the admiral R package for creating ADaMs - Ben Straub Abstract
• {Admiral} – the {dplyr} of the Pharmaceutical Industry - Stefan Pascal Thoma, Edoardo Mancini Abstract

See PR here

News devs to description File and old devs to acknowledgements - NB: check admiraldev as well

• Fanny Gautier
• Lina Patil

Devs to moved to acknowledgments (not actively working on admiral anymore) at the bottom of README:

• Adam Forys

New acknowledgements

• Sai Janardhanswami
• Phil Webster
• Nancy Brucken

Review FAQs

• Check for outdated info
• Chances to consolidate information or remove
• Possible to link to other information to help minimize upkeep

Polish News

• Each news item should have a linked issue
• Check for consistency and grammar

[bms63]

I'm going to move this to a Discussion as we have a bunch of release tasks that should be compiled into one place.

[bms63]

Hi all, @pharmaverse/admiral

I think building a Discussion around Release is needed. There are a lot of small tasks that get separate issues/PRs that I think should be done all in one PR. Sometimes we even forget to do them.

Do you see any other tasks that should be set up for a release? Some of these are form the usethis package and others are ones that we do specific to admiral. Please drop anything that needs to be added into this discussion and I will add in

[ddsjoberg]

Very good idea!

[manciniedoardo]

I've done the conference and contributors updates and linked the corresponding PRs - if anyone does any other bits please use the same branch and PR

[bms63]

@pharmaverse/admiral @pharmaverse/admiral_comm any minor contributors want to take a swing at working on this list? You can even submit the package and I can approve it. A nice learning experience for moving a package to CRAN.

It would be nice to work with on polishing this list and clarifying stuff so others can do this task in case I am taken by the bugs!!

[bms63]

@manciniedoardo here is admiralonco paper https://www.pharmasug.org/us/2024/papers.html#ST-461

[bms63]

Actual paper

https://www.[pharmasug.org/proceedings/2024/ST/PharmaSUG-2024-ST-461.pdf](https://www.pharmasug.org/proceedings/2024/ST/PharmaSUG-2024-ST-461.pdf)