Skip to content
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

Closed
seabbs opened this issue Feb 15, 2024 · 7 comments · Fixed by #653
Closed

CRAN release #552

seabbs opened this issue Feb 15, 2024 · 7 comments · Fixed by #653

Comments

@seabbs
Copy link
Contributor

seabbs commented Feb 15, 2024

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.

@sbfnk
Copy link
Contributor

sbfnk commented Feb 16, 2024

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 dist_spec necessitated by the {rstan} update).

@sbfnk sbfnk modified the milestone: CRAN v1.5 release Feb 16, 2024
@seabbs
Copy link
Contributor Author

seabbs commented Feb 19, 2024

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.

@sbfnk
Copy link
Contributor

sbfnk commented Feb 20, 2024

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?

@seabbs
Copy link
Contributor Author

seabbs commented Feb 20, 2024

Agree. Its at essentially the same point as #538 can happen imo

@sbfnk
Copy link
Contributor

sbfnk commented Feb 21, 2024

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.

@sbfnk
Copy link
Contributor

sbfnk commented Mar 4, 2024

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.

@sbfnk sbfnk mentioned this issue Mar 4, 2024
18 tasks
@sbfnk
Copy link
Contributor

sbfnk commented Mar 12, 2024

Tentatively:

Other minor issues can slot in where they fit in and major ones left to later releases.

@sbfnk sbfnk added this to the CRAN v1.5 release milestone May 3, 2024
@sbfnk sbfnk mentioned this issue May 7, 2024
7 tasks
@sbfnk sbfnk linked a pull request May 7, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants