Hi, inline On 1/31/07, Matthew Flanagan <[EMAIL PROTECTED]> wrote: > The Django buildbot slave is currently running inside a Solaris 10 > zone so it is virtualized...kind of. > > Let me clarify that testing python 2.3 and 2.4 would require a > separate buildbot master than pybots unless you can talk the pybots > maintainer into running 2.3 and 2.4 tests as well. Why don't you join > the pybots mailing list and ask?
As far as I know pybots sets new build jobs when changes occur in the python code base, so If we want to launch build jobs on new commits on django/trunk we'd need to setup a separate master anyway, wouldn't we? Having 2.3 and 2.4 there would make it possible to test django/trunk when commit occur there but not when commit occur on django's SVN. And I think that the original comment of this thread from Michael was to keep django's trunk tested on every commit and trying to test patches from TRAC before they get commited. In this scenario, am I wrong or we do need a separate master? Cheers, Marc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
