Hi Anthony, > 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. I see. > 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 Thank you for suggestion. > Neither is what you're asking for, but it's what we have today. Zac might have additional thoughts. Zac, do you have any thought? Best, Satoru _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |