  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`
  
  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.
  
  We trust that approach makes sense.
  
  ### Deprecating CoreAPI Schema Generation.
  
 
</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 We trust that approach makes sense.
 </s> add ## Feature Roadmap </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 You should migrate to using the new OpenAPI based schema generation as soon as you can.
 </s> add 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> remove ### Deprecating CoreAPI Schema Generation.
 </s> add Given that our OpenAPI schema generation is a new feature, it's likely that there
will still be some iterative improvements for us to make. There will be two
main cases here:
---
  core framework.
  
  There are two kinds of changes that easily predictable:
  
---
---
---
---
---
---
---
  
  We trust that approach makes sense.
  
  ### Deprecating CoreAPI Schema Generation.
  
keep keep keep keep replace replace replace replace 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