CRAN release

[seabbs]

its been 10 months since the last release since when multiple changes have occurred to the main branch. We need to urgently do a CRAN release once the recently identified bugs in #427 and the metrics table have been fixed. This will enable us to warn users now that a dev version is coming and to ask for any feedback on it. We could consider putting in an .onLoad rlang message about this (i.e that will show every 8 hours) given the scale of the change we are proposing. I think we should also give a date for releasing the updated develop version to CRAN so that users can be prepared (and then actually stick to this).

[seabbs]

@nikosbosse I hadn't realised that we had had no small releases in nearly a year. I think this is highest priority.

[seabbs]

I see 8 releases since 1.1.0 with releases up to 1.2.0 getting a GitHub release and 1.2.1 being used as the "release" pkgdown documentation. This means that all documentation is mismatched with CRAN with no way for users to find the correct documentation or in most cases even to tell.

[seabbs]

@sbfnk for visibility.

[nikosbosse]

To make sorting through the PRs a bit easier, these are the PRs that I think we should merge before the update:

• Issue #427: Fix error in set_forecast_unit() that occurs when input is not a data.table #487
• Issue 428 fix metrics table #489
• Issue #486: Add startup message for a new CRAN release #490
• optional: Create a PR template #491

Other than that I think everything is good to go for a release.

[nikosbosse]

Another PR needed to fix a few check issues on CRAN: #505

[seabbs]

Leaving this open until we:

• On CRAN
• Have a GitHub release
• Have a non-dev version of the docs that match the CRAN release

[nikosbosse]

Which docs are you referring to? I.e. are there any docs you think need updating immediately before the CRAN release?

[seabbs]

pkgdown