Hi Cameleers, Our current practice is that over time we would remove older versions of documentation, we do this usually after a release of the new version. We keep the LTS versions but we remove the older visions. Sometimes we do this vigilantly, sometimes it takes a while till we notice that an older version is still being published.
Overall we do this for one primary reason, the build performance is directly tied to the number of Antora components/branches being built. If the build took a constant amount of time, regardless of the number of components/branches being built we would probably leave more older versions around. There is also some maintenance to keeping older versions in case where we make a change on the website that is not backward compatible and it breaks the older version -- but I don't think we have had this issue thus far. This has recently been discussed (on Zulip or a GitHub issue, I can't seem to find), a Camel user was asking about older versions of the documentation; and again in the last few days the build was failing as we pointed to an older version of the documentation from one of the blog posts. I think we should discuss how we handle this, and explain our policy somewhere on the website. What do you think, should we keep doing as we have been doing and remove older versions? Should we keep all/more versions around? Can someone think of a way we could keep the older versions around and not jeopardize the build performance? zoran -- Zoran Regvart
