michaelsembwever commented on PR #170:
URL:
https://github.com/apache/cassandra-website/pull/170#issuecomment-1793532757
> I don't have a preference where this documentation lives. I'd just like it
to be updated with information on the recent changes in how builds work.
That would be an argument to have it versioned :-)
No strong opinions here, the trade-offs I see are
- versioned: simpler to read, just go to the version you are working with
and read half as much content. Less error-prone, and an easier page to maintain.
- unversioned: one place to learn how it works in all branches. more to
read, more cognitive load. if working with multiple branches (e.g. forward
merging) you have to do this anyway.
I question I have is if it's unversioned then what's happens to the docs on
dependency version for branches that are no longer maintained. The code is not
deleted but are we then deleting the documentation to it ? This isn't just
archival purposes, we do still (in exception circumstances) apply CVE fixes to
past branches (and the older branches are often those even the experienced devs
need to refresh their memories on how things worked…)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
