Skip to content

CRAN release requirements #67

@pearsonca

Description

@pearsonca
  • add CI/CD for testing, linting, check as cran, others?
  • finalize API - what's in, what's out
  • open capability desires - decide what is in vs out (prefer out), and then ensure API supports future addition without breaking changes (e.g. automatically inferred from data, provided as a mode = ... argument which will add more valid values in the future, etc)
    • support multi-location [both parallelization + information pooling],
    • forecasting other objectives [only support counts currently, want proportions etc])
  • any required vignettes/documentation (e.g. is the forecasting intro / decision tree needed?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions