In the past two years, I've put a lot of effort into porting the following
to Python 3:
Twisted:
https://www.slideshare.net/CraigRodrigues1/the-onward-
journey-porting-twisted-to-python-3
Buildbot:
https://github.com/buildbot/buildbot/pulls?utf8=%E2%9C%93&;
q=is%3Aclosed%20is%3Apr%20author%3Arodr
The question most relevant to this list is, what are the consequences on
the slave maintainers? Assuming we convert the master, will the slaves
be required to run python3/0.9? (That would certainly be desirable,
but would it be required?)
Are there advantages for the slave maintainers in the new
When another project tried to convert from Buildbot 0.8 to 0.9 earlier
this year, it was a total disaster and had to be reverted. I don't
know if 0.9 has improved substantially since then.
My experience is that 0.9 invested a lot of effort to make the UI
pretty, but it was much less usable. It al
I got involved with the Buildbot project only this year (focusing on Python
3 porting).
I am aware of previous reports of performance problems with buildbot nine,
but that is a bit before my time.
I believe that the earlier performance problems have been addressed.
On the buildbot-users mailing l
On 21 September 2017 at 03:49, Craig Rodrigues wrote:
> The references implementation of buildbot is being actively used to build
> buildbot
> itself, and highlights integration with GitHub Pull Requests:
Just noting that while the PR support in Buildbot 0.9 is definitely a
nice feature, we can't
