This is just a heads up since clearly some committers must be unaware: checkins of the last two days have created 27 (yes, twenty-seven) new test case failures for Oracle. I had been working on cleaning up the existing few failures for the Oracle backend, but unless those who actually committed the weekend's changes are able to look at this, Oracle should not be included in the 1.0 release IMHO.
I realize running all the backends (and all three pythons) to check for regression failures before committing code is onerous. However, that's what I do, and now I'm reminded why. It's not enough to see that the code runs on sqlite or postgres and call it a day. Here is Leo Soto's buildbot, so you can see what I'm talking about: http://certenium.ingenium.cl:8080/hudson/job/django-trunk/ I'll do my best to fix some of these as time permits, but I'm hoping others will pull together to rectify this quickly. Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
