Release simtrial 0.4.0

[nanxstats]

Prepare for release

• [x] Check current CRAN check results
• [x] Check licensing of included files
• [x] Review pkgdown reference index for, e.g., missing topics
• [x] Bump version
• [x] Update cran-comments.md (optional)
• [x] Update NEWS.md
• [x] Review pkgdown website
• [x] urlchecker::url_check()
• [x] Check with local machine
• [x] Check with GitHub Actions
• [x] Check with win-builder

Submit to CRAN

• [x] Draft GitHub release
• [x] Submit to CRAN via web form
• [x] Approve emails

Wait for CRAN

• [ ] Accepted :tada:

[jdblischak]

We have multiple PRs currently open (#229, #230, #233). If we have until May 4th to submit the update to CRAN, which of these PRs do we want to include?

[LittleBeannie]

We have multiple PRs currently open (#229, #230, #233). If we have until May 4th to submit the update to CRAN, which of these PRs do we want to include?

I guess we can at least merge #233 , which is only 1 line change of codes. Both #229 and #230 are for sim_gs_n. I will check with Keaven if he agrees to merge or plan to test them and save them for the next CRAN release.

[nanxstats]

We received some feedback from the bshazard maintainers that they will resubmit to CRAN soon. Let's wait a few days but still make a plan on what to merge. If nothing happens until next week, we make a release.

[LittleBeannie]

Thanks for the summary, @nanxstats!

I discussed the 3 open PRs with Keaven during the lunch hour and arrived at the conclusion that #233 will be in this CRAN release. And #230 and #229 will save for next CRAN release. Hope this plan works for both you and @jdblischak.

[nanxstats]

Since the noSuggests checks failed and 0.4.0 was rejected by CRAN, we will make another release (0.4.1).