On 9/22/07, Michael Radziej <[EMAIL PROTECTED]> wrote: > > On Sat, Sep 22, Russell Keith-Magee wrote: > > > Sorry for the inconvienience. > > Oh come on ... go ahead and let's have a bit more of these buglets, so that > the rest of us feel less bad for proposing wrong patches ;-)
Oh... ok then. I've just committed [6405] which randomly renames 1 in 10 variables in the Django source tree. Have fun :-) (for the humour impaired - only kidding) > BTW, wouldn't it be nice (TM) if new commits first went to side branch and > only get committed to trunk after the buildbot has given green light? I have > no idea if this is feasible ;-) There is a class of bugs that will never get caught by this approach - e.g., changes to the django-admin command line handling. However, it would be useful for everything that doesn't fall in to this edge case. I have a vague recollection that this can be done in SVN as a pre-commit trigger - i.e., commits are received and applied, but the commit isn't actually made effective until the tests all pass. It is probably worth opening a ticket so that this idea doesn't get forgotten. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
