Include Available Version markers when documenting new features

Pages affected

• Manipulating Eager Loading Queries
• Validation constraints via Symfony Validator

Description

Often documentation for new features lands in this repo (and is published) before the version it becomes available in is shipped. Even after it ships, some projects may not be updated immediately. This can create some confusion when a developer discovers and attempts to reference documentation for a feature that isn't yet available in their project.

To combat this, I propose introducing a guideline to encourage the inclusion of an 'Available from x.y' flag above any newly created documentation. In addition, I'd suggest we prune these flags when branching a new major version of the docs, since all flagged documentation can be assumed to be current at that point.

Validations

• Check that there isn't already an issue that reports the same problem

Start with the two affected pages: Manipulating Eager Loading Queries and Validation constraints via Symfony Validator. Review how documentation is versioned and branched, then define where the “Available from x.y” guideline and markers belong. Done means the guideline is documented and the proposed markers and pruning approach are consistently addressed.