Manual talk:Parser cache/Serialization compatibility

Make the compatibility policy less strict?

It may be worth loosening the compatibility policy so that we maintain parser cache compatibility only for one LTS release; if an upgrade from two LTS releases ago is required, then the parser cache must be cleared.

I think this would better match actual practice, as I don't think we've generally maintained full ParserCache compatibility as far as two LTS releases back -- we can serialize/unserialize the data, but (eg) table of contents migrated from getTOCHTML() to the getSections() so table of contents would be missing (and improperly language converted) if you loaded ParserCache data from "too long ago". cscott (talk) 16:12, 23 April 2024 (UTC)