Docs should reflect latest version "tested against" for touchpoints with different tools/frameworks/platforms #2578
Labels
Component: Documentation 📄
Issue/PR for markdown and API documentation
Milestone
Something that occurs to me as I complete #2435 is that we don't typically state the latest version of something we integrate with/deploy to that we tested.
I was looking to see what Airflow version our
kedro-airflow
plugin was tested for, and couldn't find it, for example. We don't really say this in any of our docs, but deployment is a particular area where it would help the reader to know what definitely works and to gauge how old the docs are by how big the gap is between "tested against" version and current version.This (sort-of) follows on from my thinking that we need a way to reflect the latest signficant updates on a documentation page so readers aren't guessing from change history.
I'm not sure of the exact solution right now, but am dropping this here to think about. It may simply be asking folks to add the extra information to pages where there are touchpoints, but if there's a more elegant solution, I'm up to hear about it.
The text was updated successfully, but these errors were encountered: