For HADES users requiring more stability we should create stable snapshots of all latest HADES packages at that point in time including their dependencies. As a start, this snapshot could be provided in the form of a renv lock file. This snapshot should require that all HADES packages pass R Check (as also proposed in https://github.com/OHDSI/Hades/issues/13 ). Additional tests could be performed as well, and there's even the idea of defining a HADES-wide demonstration study that is executed with a snapshot to demonstrate its working.
A frequency of twice a year seems reasonable. Possibly we could sync with R releases.
For HADES users requiring more stability we should create stable snapshots of all latest HADES packages at that point in time including their dependencies. As a start, this snapshot could be provided in the form of a renv lock file. This snapshot should require that all HADES packages pass R Check (as also proposed in https://github.com/OHDSI/Hades/issues/13 ). Additional tests could be performed as well, and there's even the idea of defining a HADES-wide demonstration study that is executed with a snapshot to demonstrate its working.
A frequency of twice a year seems reasonable. Possibly we could sync with R releases.