1.1.0 checklist

[kyle-messier]

• README - reduce installation options to CRAN and pak

  • 5d29049

• functions exposed to the cran user manual #123

  • b96bb64

• Flexible column retention in calc_*(locs = )

  • Will allow for |> and %>% operators for combining covariate data frames from different sources
  • Temporal dimension in calc_<> functions #112

• Remove the figure on contributing. Move contributing down towards the bottom of the readme as this isn't typically so prominent.

• Add a link and mention to CHORDS. Currently the connection to CHORDS via the dual hex is unclear.

[mitchellmanware]

@kyle-messier @eva0marques @eva0marques

Going forward I think we should only submit new versions to CRAN for major (ie. 1.0.0 -> 2.0.0) and minor (ie 1.0.0 -> 1.1.0) changes, not for small patches. Patching the main branch of GitHub repository is good for tracking fixes and documenting version progression, but based on the CRAN re-submission policy we should be submitting formal updates "no more than every 1–2 months".

I think we will get some real bugs and important patches as the package is used more, so 1.1.0 will probably be upon us soon.

[kyle-messier]

@mitchellmanware That is reasonable. I'll update the issue name