  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.
  
  The in-built docs that were introduced in Django REST Framework v3.5 were built on CoreAPI. These are now deprecated. You may continue to use them but they will be **removed in Django REST Framework v 3.12**.
  
 
</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 * 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 ### 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: </s> remove The in-built docs that were introduced in Django REST Framework v3.5 were built on CoreAPI. These are now deprecated. You may continue to use them but they will be **removed in Django REST Framework v 3.12**.
 </s> add * Expanding the supported range of OpenAPI schemas that are generated by default.
* Improving the ability for developers to customize the output. </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.
## Feature Roadmap
  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.
  
## Feature Roadmap
  
  ### Deprecating CoreAPI Schema Generation.
  
  The in-built docs that were introduced in Django REST Framework v3.5 were built on CoreAPI. These are now deprecated. You may continue to use them but they will be **removed in Django REST Framework v 3.12**.
  
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