Hi Eric
That's a good point. As the doc is probably the same on minor releases
(1.0.x), I agree to publish doc only for major releases.
As soon as we have a consensus here, I will create a PR to clean up.
Thanks !
Regards
JB
On Thu, Aug 21, 2025 at 8:28 PM Eric Maynard wrote:
>
> Hi all,
>
> I
+1 for that logic with one caveat: if we do follow a release train model,
in the best case, we would cut a new `X.Y.0` release every month. And that
might make the docs disappear quickly.
Example: assume we release 1.1.0 in August and do not have to do any patch
release. It follows that we relea
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 a
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 release
