  * A metadata API that allows you to customize how `OPTIONS` requests are handled by your API.
  * A more compact JSON output with unicode style encoding turned on by default.
  * Templated based HTML form rendering for serializers. This will be finalized as  public API in the upcoming 3.1 release.
  
  Significant new functionality continues to be planned for the 3.1 and 3.2 releases. These releases will present simple upgrades, without the same level of fundamental API changes necessary for the 3.0 release.
  
  Below is an in-depth guide to the API changes and migration notes for 3.0.
  
  ---
  
 
</s> remove **TODO: Needs documenting.**
 </s> add REST framework also now includes explicit validator classes for validating the `unique_for_date`, `unique_for_month`, and `unique_for_year` model field constraints. These are used internally instead of calling into `Model.full_clean()`.

These classes are documented in the [Validators](../api-guide/validators.md) section of the documentation.
Significant new functionality continues to be planned for the 3.1 and 3.2 releases. These releases will correspond to the two [Kickstarter stretch goals](https://www.kickstarter.com/projects/tomchristie/django-rest-framework-3) - "Feature improvements" and "Admin interface". Further 3.x releases will present simple upgrades, without the same level of fundamental API changes necessary for the 3.0 release.
  * A metadata API that allows you to customize how `OPTIONS` requests are handled by your API.
  * A more compact JSON output with unicode style encoding turned on by default.
  * Templated based HTML form rendering for serializers. This will be finalized as  public API in the upcoming 3.1 release.
  
Significant new functionality continues to be planned for the 3.1 and 3.2 releases. These releases will correspond to the two [Kickstarter stretch goals](https://www.kickstarter.com/projects/tomchristie/django-rest-framework-3) - "Feature improvements" and "Admin interface". Further 3.x releases will present simple upgrades, without the same level of fundamental API changes necessary for the 3.0 release.
  
  Below is an in-depth guide to the API changes and migration notes for 3.0.
  
  ---
  
keep keep keep keep replace keep keep keep keep keep
 Fill in TODOs for 3.0 beta release notes 
docs/topics/3.0-announcement.md