  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`
    or `AutoSchema`
  
 
</s> remove 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.
 </s> add There are some great third party options for documenting your API, based on the
OpenAPI schema. </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 * Subclass `SchemaGenerator` for schema-level cusomizations.
* Subclass `AutoSchema` for view-level customizations.
 </s> add ### API Documentation </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 We have removed the old documentation for the CoreAPI based schema generation.
You may view the [Legacy CoreAPI documentation here][legacy-core-api-docs].
 </s> add It's also possible that we'll end up implementing API documentation and API client
tooling that are driven by the OpenAPI schema. The `apistar` project has a
significant amount of work towards this. However, if we do so, we'll plan
on keeping any tooling outside of the core framework.
See the [Documenting you API](../topics/documenting-your-api.md) section for more details.
  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.
  
See the [Documenting you API](../topics/documenting-your-api.md) section for more details.
  
  * General improvements which fill in gaps in the automatic schema generation.
  * More use-case specific adjustments, which adjust the API of `SchemaGenerator`
    or `AutoSchema`
  
keep keep keep keep 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