From fcaaff9862a93efe8ccd2a23b7e38d62dcf7a9d2 Mon Sep 17 00:00:00 2001
From: Mariusz Felisiak <felisiak.mariusz@gmail.com>
Date: Tue, 24 Sep 2019 13:03:40 +0200
Subject: [PATCH] [3.0.x] Refs #27910 -- Doc'd support for enumeration types
 serialization in migrations.

Backport of aad46ee274b0e294ac055cc199e6595de4ef4164 from master
---
 docs/topics/migrations.txt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index adbe1d72ea..fc18593dbd 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -678,6 +678,7 @@ Django can serialize the following:
 - :func:`functools.partial` and :class:`functools.partialmethod` instances
   which have serializable ``func``, ``args``, and ``keywords`` values.
 - ``LazyObject`` instances which wrap a serializable value.
+- Enumeration types (e.g. ``TextChoices`` or ``IntegerChoices``) instances.
 - Any Django field
 - Any function or method reference (e.g. ``datetime.datetime.today``) (must be in module's top-level scope)
 - Unbound methods used from within the class body