EpiNow2 2.0.0 roadmap

[sbfnk]

It might be good to put together a development roadmap for EpiNow2 2.0.0. Current open Issues/Discussion would suggest

New features:

• Fit to multiple observation time series (see design discussion at Fit to multiple time series and fold in secondary model #371)
• Allow for fitting the susceptible population #408
• rename models and add (simple) covariate interface switch to directly calculated growth rate and extend model options, take 2 #345
• replace estimate_delays with estimate_dist with better discretisation estimate_delays -> estimate_dist #350 Discretisation #411
• add an optimisation option Optimisation #403

User interface

• streamline S3 classes #451
• Interface unification with epinow2() wrapper function? #191 (if deciding to do) not doing for now
• reported_cases_opts() #346
• Reconsider distribution interface. #382
• Deprecate get_incubation_period and get_generation_time due to reimplementation elsewhere #390
• Distribution max is really the length #410

Bug fixing

• estimate_secondary prevalence model does not recover the synthetic parameters #349
• Edge case breaking summary stats output #392
• Failing tests on Windows #420

Internal improvement

• Put duplicated stan code in chunks #381
• Add input validation #337
• Use delays_lp() in estimate_truncation #348

Documentation

• Clarify documentation for passing uncertainty from estimate_truncation to estimate_infections #367 which could go nicely with Paper writeup #353

Quite a lot in there so some of these (especially the new features) may warrant intermediate releases.

[jamesmbaazam]

This has now been set up as a project board here https://github.com/orgs/epiforecasts/projects/7. I'm unable to make it public, I guess because I don't have those rights on the Epiforecasts org. @sbfnk can you make it public?

Also, would you like us to add all new issues to the board manually or do we want to do it automatically using the project workflows rules?

[sbfnk]

This has now been set up as a project board here github.com/orgs/epiforecasts/projects/7. I'm unable to make it public, I guess because I don't have those rights on the Epiforecasts org. @sbfnk can you make it public?

Done

Also, would you like us to add all new issues to the board manually or do we want to do it automatically using the project workflows rules?

If they are added automatically can we then use the project board to decide whether they get added to the release or not? At some point we'll want to release and leave some issues behind.

[jamesmbaazam]

If they are added automatically can we then use the project board to decide whether they get added to the release or not? At some point we'll want to release and leave some issues behind.

Yes, they can all go on the board and initially without a status. We can then set rules to move them across the board, for example, when a PR is opened to address them.

Currently, we have to assign it the "CRAN v2.0 release" milestone to move it to the board. I think that should work.

[sbfnk]

Closing as superseded by #552 and associate project boards.