From 1556a67c65c336ab12961c6123b129ac10e729b8 Mon Sep 17 00:00:00 2001
From: David Vaz <davidmgvaz@gmail.com>
Date: Fri, 27 Sep 2019 04:00:32 -0700
Subject: [PATCH] [2.1.x] Fixed #30216 -- Doc'd that BooleanField is no longer
 blank=True in Django 2.1.

Backport of a6972e88547ad5a51592f2b6d5046754c4b59394 from stable/2.2.x
---
 docs/ref/models/fields.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index ffd2387739..48980a92b4 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -459,6 +459,10 @@ isn't defined.
     use :class:`NullBooleanField` instead. Using the latter is now discouraged
     as it's likely to be deprecated in a future version of Django.
 
+    In older versions, this field has :attr:`blank=True <Field.blank>`
+    implicitly. You can restore the previous behavior by setting
+    ``blank=True``.
+
 ``CharField``
 -------------