  
  * Subclass `SchemaGenerator` for schema-level cusomizations.
  * Subclass `AutoSchema` for view-level customizations.
  
  We'll wait to see what subclasses people actually come up with, for the
  customizations they actually need, before trying to bring that back into the
  core framework.
  
  There are two kinds of changes that easily predictable:
  
  * General improvements which fill in gaps in the automatic schema generation.
  * More use-case specific adjustments, which adjust the API of `SchemaGenerator`
 
</s> remove There are two kinds of changes that easily predictable:
 </s> add See the [Documenting you API](../topics/documenting-your-api.md) section for more details. </s> remove * Subclass `SchemaGenerator` for schema-level cusomizations.
* Subclass `AutoSchema` for view-level customizations.
 </s> add ### API Documentation </s> remove * General improvements which fill in gaps in the automatic schema generation.
* More use-case specific adjustments, which adjust the API of `SchemaGenerator`
  or `AutoSchema`

We'll aim to bring the first type of change quickly in point releases. For the
second kind we'd like to adopt a slower approach, to make sure we keep the API
simple, and as widely applicable as possible, before we bring in API changes.
 </s> add --- </s> remove So, for a fresh start with `OpenAPI`, customizing schema generation has two
simple rules:
 </s> add For more details, see the [API Schema documentation](../api-guide/schemas.md). </s> remove For v3.7 (with `CoreAPI`) we tried to anticipate customizations that people
were likely to need. (Introducing `manual_fields` and `ManaualSchema`, for
example.) These were under-utilised. They weren't the right abstractions.
 </s> add For specific per-view customizations, you can subclass `AutoSchema`,
making sure to set `schema = <YourCustomClass>` on the view.
There are some great third party options for documenting your API, based on the
OpenAPI schema.
  
  * Subclass `SchemaGenerator` for schema-level cusomizations.
  * Subclass `AutoSchema` for view-level customizations.
  
There are some great third party options for documenting your API, based on the
OpenAPI schema.
There are some great third party options for documenting your API, based on the
OpenAPI schema.
There are some great third party options for documenting your API, based on the
OpenAPI schema.
  
  There are two kinds of changes that easily predictable:
  
  * General improvements which fill in gaps in the automatic schema generation.
  * More use-case specific adjustments, which adjust the API of `SchemaGenerator`
keep keep keep keep replace replace replace keep keep keep keep keep
 Version 3.10 (#6802)

* 3.10 release notes

* Version number -> 3.10

* Update translations

* Update 3.10 release docs

* Update release notes

* Delete symlink 
docs/community/3.10-announcement.md