Added note to bump stable branch docs config on release.

[carltongibson]

django_next_version in docs/conf.py should be bumped in stable branch on final
release.

[felixxm]

@carltongibson Thanks 👍 I think we should move this note to the "Pre-release tasks", maybe up to the 7th point 🤔 .

[carltongibson]

Hey @felixxm -- yes, i was pondering if it's a When creating the new stable branch task. Let's decide tomorrow. 😉

[timgraham]

I think it's fine to do when creating a new stable branch. This controls whether the version number or "Development version" appears in the versionadded/changed annotations.

Actually, it might be feasible to remove this in favor of checking django.VERSION. If the last three parts of the tuple are (0, 'alpha', 0) then it's a pre-alpha development version. It's unclear under what conditions django.VERSION can't be imported though (added in 373df56).

[carltongibson]

Hey Tim — thanks for looking — another lurker on my list 🤹‍♂️.

I've adjusted the comment to go at the creating new stable branch step (which is 9 currently).

...it might be feasible to remove this in favor of checking django.VERSION. ...

That would be better.

It's unclear under what conditions django.VERSION can't be imported though (added in 373df56).

Looking above I wonder how this could ever (excluding syntax errors and the like) fail now:

django/docs/conf.py

Lines 24 to 25 in 4a77aeb

	# Make sure we get the version of this copy of Django
	sys.path.insert(1, dirname(dirname(abspath(__file__))))

If that went wrong we'd want it to crash no? 🤔

I need to have a little dig around.

[carltongibson]

Tim's https://code.djangoproject.com/ticket/21400#comment:6 — reloading Django on the build server to get the right version. Grrr.

I think merge this for now, and see if there's an adjustment as time/bandwidth/motivation permits.

Thanks both!