CRAN release?

[Bisaloo]

The interface of this package seems relatively stable and it already went through a couple of GitHub release so it may be a good time to think about CRAN release.

From what I understand, the way the interoperability with epiparameter is set up doesn't require epiparameter to be in Imports and it could be downgraded to Suggests, which means it's no longer blocking the CRAN release.

What do you think?

[joshwlambert]

Thanks for raising this, my plan (although not communicated anywhere) is to release to CRAN at v0.4.0. The package is reaching stability by each release has contained breaking changes, and the upcoming v0.3.0 (see milestone for included features and changes) will also include breaking changes.

With the current pace of development and release cycle, I expect v0.4.0 to be ready by mid-June.

The plan is also to have {epiparameter} on CRAN before {simulist} so whichever type of dependency we list {epiparameter} as it shouldn't block a CRAN submission.

Happy to hear thoughts on this plan.