On Mon, Dec 7, 2009 at 4:59 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > Hi folks -- > > According to our timeline, we're at (a bit past, actually) the point > where we need to take a quick look at progress towards 1.2 and decide > whether the current timeline still makes sense. > > Right now, we've completed 4.5 features on the 1.2 priority list: > > * Comment admin actions (Contrib-10). > * Improved CSRF protection (Core-01). > * The first half(ish) of merging multidb (GSoC-05) > * QuerySet.exists() (ORM-10) > * Email backends (Email-01) > > Additionally, a few features are in or close to last-call stage > (multidb and the smarter if tag). > > Our current roadmap calls for large feature freeze on December 22nd, > and a complete freeze on January 26th. > > So the question is: given what we've got done, and guess at what we > will get done, is the current timeline still feasible, or should we > push the timeline? > > My opinion is that we should keep the schedule as-is. The features > we've got done so far aren't all huge and game-changing, but if we > released 1.2 with the features *as they stand right now*, it'd still > make a solid upgrade. If we can indeed get multidb merged, that'll be > a killer feature, but if it's not done I don't want to wait for it. > > Not ever release of Django needs to be a home run; I'd settle for a > base hit every time. > > Thoughts? > > Jacob > > -- > > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@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. > > >
I'd be -1 on delaying. I think having consistant releases is more important than having a grand slam every time. I'll also note that I'm very confident that multi-db will be ready for merge by then, Justin and I (ok mostly Justin) have been working on the GIS stuff, which is the last blocker. I think we've got a great release already (ok I'm biased), and with the next month we'll have to work on smaller features we can work on knocking off lots of little tickets that people care about (remember post developers hit far more small bugs than need huge new features like multidb). Also, you can add template caching (and thread safety), #6262, to the list of features that are almost ready to land (unless Russ's opinion of that patch has taken a nosedive). Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Voltaire "The people's good is the highest law." -- Cicero "Code can always be simpler than you think, but never as simple as you want" -- Me -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
