michaelsembwever commented on PR #170: URL: https://github.com/apache/cassandra-website/pull/170#issuecomment-1796146263
> Regarding EOL'd branches - aren't branches usually EOL'd when a new major comes out? Maybe we can do a docs sweep for every new major, as there's likely going to be a lot of other change happening to the docs at the same time? Well yes, that's kinda my point. We'll possibly be cleaning up docs quickly (after each major release), and then those EOL'd branches no longer have the docs for them anywhere – and that's a problem, because our EOL'd isn't "nuke them", it's just we don't have the contributor resources to maintain these older branches but they still exist and others are free to step in and work with them. For examples: we do still apply CVE to older EOL'd branches as we see fit, and Microsoft has stepped forward and said they will provide support for older branches. -- 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]
