Context Navigation

Changes between Initial Version and Version 1 of Ticket #32161

initial	v1
10	10
11	11
12		How if you're a Django Core Maintainer and live and breathe Django, the above probably looks harmless to you. However if you're not "in the know" that Django named it 3.1 instead of 3.1.0, the above looks kinda like a loosely defined install. The mere existence of 3.1 and 3.1.2 creates just enough ambiguity to be uncertain about which version is actually installed. The thought process is like "I know 3.1.2 exists so why would 3.1.0 not exists? "
	12	Now if you're a Django Core Maintainer and live and breathe Django, the above probably looks harmless to you. However if you're not "in the know" that Django named it 3.1 instead of 3.1.0, the above looks kinda like a loosely defined install. The mere existence of 3.1 and 3.1.2 creates just enough ambiguity to be uncertain about which version is actually installed. The thought process is like "I know 3.1.2 exists so why would 3.1.0 not exists? "
13	13
14	14	By using consistent semver (or any version style) you can remove this tiny amount of ambiguity and create 100% certainty and confidence.