Ideally, we should look to depend on stable package versions. The reasons why are:
When developing R packages, it is generally advisable to avoid depending on GitHub-based dependencies. Instead, using stable versions from CRAN (Comprehensive R Archive Network) is recommended. Here are the reasons why:
CRAN checks packages
CRAN packages are versioned
CRAN provides pre-compiled binaries, making installation easier (faster) for users
As a part of the
DESCRIPTION
we currently rely on GitHub remotes for a number of packages:PR #69 adds
brms
to this list as there is a bug with the non-HMC inference methods only fixed in the development version ofbrms
(https://github.com/paul-buerkner/brms/issues/1650).Ideally, we should look to depend on stable package versions. The reasons why are:
When developing R packages, it is generally advisable to avoid depending on GitHub-based dependencies. Instead, using stable versions from CRAN (Comprehensive R Archive Network) is recommended. Here are the reasons why:
I don't know the extent of barriers to doing this. For the
brms
one it's a matter of time until the fix is on CRAN.