I talked with Zach on IRC. He wants to move everything to buildbot nine right now. Well, if he takes the responsability, I'm totally fine with that. Let me elaborate.
If a few workers are broken, we can skip them to give time to the buildbot owner to fix them, or give us time to fix their config. It's not a blocker issue. A blocker issue would be to break *everything*. This option seems unlikely since I'm seeing a working buildbot nine instance. Moreover, as Zach wrote me on IRC, we *can* revert to buildbot 0.8. So ok, let's move "everything" (the server) to buildbot nine! Yahoo! 2017-10-06 22:33 GMT+02:00 Craig Rodrigues <rodr...@crodrigues.org>: > Based on my experiments, I think it is safe to perform the migration as > follows: > > 1. Update the buildbot master to buildbot 9 + Python 3. Leave the > buildbot workers/slaves alone. They should be > able to successfully connect to the new buildbot master and work. Oh great, you confirmed that we can upgrade the server right now, and only upgrade workers later. Nice. Victor _______________________________________________ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
