Skip to content

release 1.14.10 #5709

@jangorecki

Description

@jangorecki

We are getting errors on CRAN due to changes in R-devel, therefore we should provide patched version for the current moment, rather then trying to push current master. Release of current master can as well follow the patch release, but releasing master should not be blocking patch release. There is still at least 1 pending issue to resolve in master before it will be ready for CRAN.

Ideally it will be the last release before moving to new governance structure (ultimately that depends on breaking changes in R-devel or breaking changes in CRAN policies).

Issues on a 1.14.9 (1.14.10) milestone should be merged to hotfix1.14.10 branch, and later on to master as well.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions