-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRAN release #552
Comments
Question is whether we do this now or wait until the 2.0.0 release (#423) is ready. Given quite substantial further development that will be needed especially to update the observation model and covariate interface I agree that there might be a case for an intermediate release as long as we're fairly confident that features have stabilised (avoiding repeating the introduction/deprecation of |
Yeah I think its basically as we at a point with few breaking changes but new features that people could use before things get dangerous? I think we probably are. |
Yes, I agree. Probably worth just waiting until we're happy the distribution interface and then going through some of the minor issues for release? |
Agree. Its at essentially the same point as #538 can happen imo |
There now is a project board at https://github.com/orgs/epiforecasts/projects/9 with the fairly minor issues that might be nice to tackle for this. |
There are still quite a few updates in the 2.0.0 plan. It might be nice to plan for a few intermediate releases which brings in each of these separately, followed by a "clean" 2.0.0 release where all deprecated functions are removed. |
Tentatively:
Other minor issues can slot in where they fit in and major ones left to later releases. |
We (mostly thanks to @sbfnk) are starting to accumulate a lot of nice new features all (I think) are well implemented enough not to break backwards compatibility. Given that we should likely plan for a CRAN release in the near future. Especially as some of the larger changes may have to lead to breaking changes.
The text was updated successfully, but these errors were encountered: