The docs aren't necessarily structured that way, i.e. there isn't a 17.2.6 docs site as such. We try to document changes in behavior in sync with code, but don't currently have a process to ensure that a given docs build corresponds exactly to a given dot release. In fact we sometimes go back and correct things for earlier releases.
For your purposes I might suggest: * Peruse the minor-version release notes for docs PRs * Pull the release tree for a minor version from git and peruse the .rst files directly Neither is what you're asking for, but it's what we have today. Zac might have additional thoughts. > On Jul 11, 2023, at 23:44, Satoru Takeuchi <satoru.takeu...@gmail.com> wrote: > > Hi, > > I have a request about docs.ceph.com. Could you provide per minor-version > views > on docs.ceph.com? Currently, we can select the Ceph version > by using `https://docs.ceph.com/en/<version>". In this case, we can > use the major > version's code names (e.g., "quincy") or "latest". However, we can't > use minor version > numbers like "v17.2.6". It's convenient for me (and I guess for many > other users, too) > to be able to select the document for the version which we actually use. > > In my recent case, I've read the mclock's document of quincy because I > use v17.2.6. > However, the document has changed a lot from v17.2.6 to the quincy's latest > one > because of the recent mclock's rework. > > Thanks, > Satoru > _______________________________________________ > ceph-users mailing list -- ceph-users@ceph.io > To unsubscribe send an email to ceph-users-le...@ceph.io _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
