On Thu, Sep 17, 2009 at 4:35 PM, Simon Willison <si...@simonwillison.net> wrote: > > On Sep 13, 12:52 pm, Russell Keith-Magee <freakboy3...@gmail.com> > wrote: >> Although the branch isn't ready for merge yet, the code that is >> present is all up to spec. I think the sprints have produced workable >> solutions for the outstanding problems; fixes implementing the >> solutions we discussed should be forthcoming shortly. > > With my cowboy hat on... what are the disadvantages to merging this to > trunk /now/ and fixing the remaining outstanding issues there? It > might make it easier to get the other SoC branches compatible with > this one (which sounds to me like it makes the most far-reaching > changes) and it would encourage the wider community to help check that > everything really is backwards compatible. > > <cowboy>
Howdy Pardner... :-) My hesitation here is that there one of the outstanding changes is a fairly big refactor of the way the SQL backend handles queries, and I want to make sure it's right before we inflict it on the world. In particular, I need to make sure that the needs of Oracle and contrib.GIS aren't broken by the refactor. I don't want to commit the patch only to have to roll large parts of it back in the near future. To keep your inner cowboy happy - I'm not actually anticipating that much of an overlap problem with the other GSoC branches. Although the changes are fairly extensive, they are mostly with internals, and not in areas that the other GSoC branches should be touching, such as database backends, details of connection handling, use of connections by management commands. The m2m refactoring patch (which is a prerequisite for the multi-db work) could be committed now without any major problems. Yours, Russ (The lone cowboy of the West) %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. 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 -~----------~----~----~----~------~----~------~--~---
