id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
23283	Provide an explicit default for BooleanField used in the documentation	Baptiste Mispelon	Ola Sitarska	"In Django 1.6, we changed the default value for a `BooleaField` from `False` to `None`.
Having a `BooleanField` without a default now results in warnings when running the `validate/check` command.

However, our documentation uses some `BooleaField` in a few examples (see [1] for example) but they don't have a default value.

I propose that all usages of `BooleanField` in our documentation provide an explicit default (`False` most likely) so that running the code doesn't raise any warnings.

[1] https://docs.djangoproject.com/en/dev/topics/db/models/#multi-table-inheritance"	Cleanup/optimization	closed	Documentation	dev	Normal	fixed			Accepted	1	0	0	0	1	0