Plan next milestone + release date (post-CRAN v0.1.0)

[WestonVoglesonger]

@pearsonca @csmith701 — imuGAP 0.1.0 is now accepted and live on CRAN 🎉

I've closed the CRAN release milestone (all 31 issues done). Time to define the next one and a target date.

Current state of "Post CRAN MVP" (milestone #2)

Open issues currently slotted there:

• predict spanning groups #79 — predict spanning groups
• Refactor active models to use modular includes (move off monolithic *_shared.stan) #60 — Refactor active models to use modular includes (move off monolithic *_shared.stan)
• Support default weight = 1 for single-row populations #43 — Support default weight = 1 for single-row populations
• guidance for particular "school" circumstances #5 — guidance for particular "school" circumstances
• Move latent_params_sim into the tracked/static data (disentangle coverage from target_sim) #105 — Move latent_params_sim into tracked/static data (CI cost cleanup)

Also open but unmilestoned: #94 (user feedback), #99 (grand ideas), #100/#101 (cmdstanr backend — PR open).

Decisions needed

1. Scope — which of the above are in scope for the next release vs. deferred? Should the cmdstanr backend (Add a cmdstanr backend option, porting the pattern from hestia #100) land in it?
2. Version — next release 0.2.0 (new features) or 0.1.1 (fixes only)?
3. Target date — set a due_on for the next milestone.
4. Rename/repurpose "Post CRAN MVP" to the chosen version, or create a fresh milestone?

Once you two settle on scope + date I'll update the milestone(s) and assign issues accordingly.

[pearsonca]

1. yes, let's aim for adding cmdstanr support
2. increment to 0.2.0 - will be expanding API, not just fixes bug let's say.
3. let's say mid Aug?
4. yep, rename to 0.2 release or some such?

[pearsonca]

re specific issues:

• tentative yes on predict spanning groups
• yes on default weight
• yes on internal refactors

Going to tag some others as well.

[WestonVoglesonger]

Handoff: I’m leaving ACCIDDA next week. @pearsonca, please take ownership of post-CRAN milestone planning and release timing, updating this tracker to reflect the flexstanr migration and current downstream priorities.