Hi Eric, It's a good point, yet for the next few months the list is probably going to be quite manageable.
I'd like to propose this logic for docs. Suppose we have a list of versions X.Y.Z. For every X, keep 3 most recent Ys and only the latest Z for each Y. As an example, after 1.1.0 is released, we'd have docs for 1.0.1 and 1.1.0. If we ever have too many major releases (X), we'll have to revisit this and sunset some of them. How does that sound? Cheers, Dmitri. On Thu, Aug 21, 2025 at 2:28 PM Eric Maynard <eric.w.mayn...@gmail.com> wrote: > Hi all, > > I was looking at the site today and noticed we have a section in the docs > for 1.0.1. On one hand, this is great to see as I'm sure we're all excited > about the release. On the other, I could imagine this list getting pretty > crowded as patch releases continue to happen. I've been wondering about the > best way to deal with this problem in the future. > > Should we release the docs by major / minor release, as in having doc pages > for 1.0.x and 1.1.x? > Could we group them somehow into subsections by minor release? > Or could we maybe just hide some releases from the dropdown menu? > Any other ideas? > > Cheers, > > Eric M. >
