Ehhm, version numbers aren't decimal numers. 2.0 doesn't have to wait for 1.9.
Maybe even drop python 2 for django 2.0? Harro On Saturday, 30 June 2012 21:25:07 UTC+2, Jacob Kaplan-Moss wrote: > > Wow. There's really a lot to think about here, and I'm only just > starting. Thanks for putting this together, Luke: I know it's been > something that's been discussed a ton, but until now nobody's really > done the due diligence to figure out exactly what the process and > ramifications would be. > > Before we do get too deep into this, however, I want to talk about > this "Django 2.0" thing: > > Clearly there will be something called "Django 2.0" at some point -- > after 1.9, if we get there, comes 2.0. However, I think it would be a > mistake to make "Django 2.0" backwards-incompatible. We've seen > countless examples -- Perl 6, Python 3, Rails 3, ... -- that these > sorts of "breaks from the past" really alienate and frustrate the > community. Over the years we've actually gotten really good at > balancing forward motion with stability. Our reputation as a stable, > reliable platform is something I'm intensely proud of. > > It's going to take a lot of work to convince me of the value of a > "break from the past" sort of approach. If this can't be done in a way > that promises a smooth upgrade path... I'm not sure it's worth doing. > > Now, that's not a vote against (at least not yet); I think we can find > balance here. I'm certainly not arguing that any backwards > incompatibilities sink the proposal. There's a certain level of > incompatibility that'll be OK, especially when the upside's so great. > External dependencies? If the ecosystem's ready (and it's getting > there), then we can adopt them without affecting most users. Changed > internals? We've already been pretty clear that the internals of the > model system is off-limits, and I think we can tolerate some changes > there. > > So: if we're going to go down this path -- and your reasons for why we > should are spot-on -- I say we have to figure out if we can minimize > the upgrade path. > > Jacob > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/qlGNeeZ9x94J. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
