Closed jdhoffa closed 7 months ago
my not-so-important opinion here is that this repo is "mature" in that it does what it's supposed to do, we've been actively using it on public facing pages for many months, and there's no unsolved problems or bugs to fix (that I'm aware of). Sure, we may decide to change up the styling, but the basic functionality is pretty stable.
Hmm, so it seems that the stage maturing
has been deprecated LOL
https://lifecycle.r-lib.org/articles/stages.html#maturing
tidyverse
folks argued that there was no real/ actionable difference between maturing
and experimental
. Either something has a stable API or it doesn't...
I think this will warrant us to more precisely define what/ how we want to define our stages
+1 for mature.
Rationale: This repo doesn't have many PRs against it, and even if it did, none of them would be introducing what we would consider "breaking changes" for the rendered HTML.
I'd say it's "stable" then since how it's used is unlikely to change, though it's content/styling might change
Sounds good :-)
Will change tomorrow when I'm back at the computer
experimental
ormaturing
here?I expect we still may want to totally revamp our
pkgdown
sites.