# 0.2.0 package pre-release
**URL:** https://community.epinowcast.org/t/0-2-0-package-pre-release/103
**Category:** Announcements
**Created:** [5 December 2022 15:28 UTC](https://community.epinowcast.org/t/0-2-0-package-pre-release/103 "2022-12-05T15:28:59Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@samabbott](https://community.epinowcast.org/u/samabbott)
#### Post date: [5 December 2022 15:28 UTC](https://community.epinowcast.org/t/0-2-0-package-pre-release/103/1 "2022-12-05T15:28:59Z")
We have nearly implemented the planned functionality for the `0.2.0` release (see here for the plan: [Changelog • epinowcast](https://package.epinowcast.org/news/index.html#epinowcast-010) and here for currently added features: [Changelog • epinowcast](https://package.epinowcast.org/dev/news/index.html#epinowcast-020)). There is some really exciting stuff in here and a lot of work from many people so really keen to get this out in the world.
I’ve made a PR (see [0.2.0 Release by seabbs · Pull Request #180 · epinowcast/epinowcast · GitHub](https://github.com/epinowcast/epinowcast/pull/180)) with the list of issues I think we need to deal with before we can make a release. It would be great if people can take a look/comment/add/remove etc. This also means that we should start planning which issues to address in `0.3.0`. For me, the key things to do are stabilise the interface (i.e [Use of enw\_ prefix](https://community.epinowcast.org/t/use-of-enw-prefix/42) and [Add data format converters · Issue #144 · epinowcast/epinowcast · GitHub](https://github.com/epinowcast/epinowcast/issues/144)), decide on and implement a definition for the max delay and get forecasting functionality implemented ([Add future forecasting ability · Issue #3 · epinowcast/epinowcast · GitHub](https://github.com/epinowcast/epinowcast/issues/3)). If possible I would also love to add non-parametric delays ([Add non-parametric reference date model · Issue #4 · epinowcast/epinowcast · GitHub](https://github.com/epinowcast/epinowcast/issues/4)) and decoupling of the expectation/reporting delay model (i.e so you can fit conditional distributions + use the expectation model on non-right truncated data - no issue for this one but we need it).
There are lots of other features we likely want. I’d really like to see people suggest some in the issues etc 🙂
In terms of where we should put the planning for `0.3.0` I am not that sure? We could make a discuss here for now and then move it to GitHub once things are more sorted out or open a meta-issue on GitHub.
---
### Author:  [@adrianlison](https://community.epinowcast.org/u/adrianlison)
#### Post date: [13 December 2022 11:52 UTC](https://community.epinowcast.org/t/0-2-0-package-pre-release/103/2 "2022-12-13T11:52:56Z")
Thanks for compiling the pre-release @samabbott ! I have commented on 0.2.0 on github.
Regarding 0.3.0 I think it would be nice to have the discussion here first, making it more accessible and visible hopefully.
---
### Author:  [@adrianlison](https://community.epinowcast.org/u/adrianlison)
#### Post date: [13 December 2022 12:02 UTC](https://community.epinowcast.org/t/0-2-0-package-pre-release/103/3 "2022-12-13T12:02:53Z")
For me, some valuable points in addition to the ones mentioned by @samabbott would be
- investing in documentation and more/better vignettes
- adding basic simulation capabilities (potentially as separate package)
- plotting estimated reporting delays and share of missing reference dates
- extending ability to specify priors
---
### Author:  [@samabbott](https://community.epinowcast.org/u/samabbott)
#### Post date: [18 December 2022 22:26 UTC](https://community.epinowcast.org/t/0-2-0-package-pre-release/103/4 "2022-12-18T22:26:58Z")
I agree with all of those suggestions. I also think we need to think more about the user journey and make sure the package is relatively friendly to the various kinds of data that people usually have.
---
### Author:  [@samabbott](https://community.epinowcast.org/u/samabbott)
#### Post date: [6 January 2023 18:08 UTC](https://community.epinowcast.org/t/0-2-0-package-pre-release/103/5 "2023-01-06T18:08:43Z")
We now have a candidate release on `main` which really needs its tires kicking (see draft release notes here: [Changelog • epinowcast](https://package.epinowcast.org/news/index.html)).
> **[GitHub - epinowcast/epinowcast: Flexible hierarchical nowcasting](https://github.com/epinowcast/epinowcast)**
>
> Flexible hierarchical nowcasting. Contribute to epinowcast/epinowcast development by creating an account on GitHub.
In particular, could people check the news item and make sure I haven’t missed anything or anyone? We are also really really crying out for a model schematic as currently we are just trying to 🤯 peoples brains I think.
I’ve also set up a meta-tracking issue for this release with some final things to do. I am going to propose we release it by writing a blog post on the [epinowcast.org](http://epinowcast.org) site which I will draft up and then post here (perhaps over the weekend or next week).
Something to note is that in fixing our R universe I have updated it so that it builds our latest release vs the latest code on `main`. This gives us a three-level release process with manual production releases via the GitHub release framework, a stable development version (i.e `main`), and an unstable development version (`develop`). This should let us have a bit more confidence about pushing out small releases rapidly.
---
### Author:  [@adrianlison](https://community.epinowcast.org/u/adrianlison)
#### Post date: [13 January 2023 16:54 UTC](https://community.epinowcast.org/t/0-2-0-package-pre-release/103/6 "2023-01-13T16:54:50Z")
Release and news look good from my side!
Fully agree that we need a model figure, maybe even two versions with different complexity. Maybe something to draft conceptually during the next meeting and then someone can produce a decent figure based on it.
Nice one with the R universe, so the idea is we can be more ruthless on `develop`? 😃
---
### Author:  [@samabbott](https://community.epinowcast.org/u/samabbott)
#### Post date: [13 January 2023 17:39 UTC](https://community.epinowcast.org/t/0-2-0-package-pre-release/103/7 "2023-01-13T17:39:57Z")
Good idea to have a brainstorm at the next meeting. Also worth discussing the kind of style we want to go for (i.e how much math).
> Nice one with the R universe, so the idea is we can be more ruthless on `develop` ? 😃
Yes exactly and have a working development version on `main`.
---
### Author:  [@samabbott](https://community.epinowcast.org/u/samabbott)
#### Post date: [16 January 2023 11:42 UTC](https://community.epinowcast.org/t/0-2-0-package-pre-release/103/8 "2023-01-16T11:42:15Z")
Made the release offical as we seem happy with it and pushed out a twoot: [Sam Abbott: "Epinowcast #rstats 📦 release 0.2.0 is now out (as…" - Fosstodon](https://fosstodon.org/@seabbs/109698678786582177)
Still drafting a release post so will share that once I have something!