Hello, Version numbers are symbolic values with no inherent meaning. As a consequence, anyone may choose to follow any convention. You're welcome to find 1.9 --> 2.0 ridiculous just as much as I'm welcome (or at least, I hope so) to find 1.9 --> 1.10 laughable ;-) Seriously, in the grand scheme of things, this doesn't matter much.
Since we have a mechanism for backwards-incompatible changes, namely the two-release deprecation process, we believe that we'll never have to pull a Python 3. In fact, we'd rather not, considering how it went. So, in order not to stay stuck at 1.xx forever, we -- the core team -- decided that the version after 1.9 would be 2.0. When I say "we decided", I mean that we had this discussion at a few DjangoCons, that most core devs found that option acceptable, and that it became tribal knowledge. No one took issue with the introduction of RemovedInDjango20Warning as the successor to RemovedInDjango19Warning. Discussions about versioning schemes are about as religious as those about text editors, so, please, let's leave it there. If one or several core devs -- I see that Shai supports 1.10 -- want to resume this holy war, let's handle it at the scale of the core team, not at the scale of django-developers. We'll be fine anyway. Thank you! -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1B1A2373-0EB3-468E-B001-1A1680371ACA%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
