"Martin v. Löwis"
martin at v.loewis.de
Sun Apr 5 20:18:33 CEST 2009
>> Ok, that's a problem. We currently run 0.7.5 on the master, and have
>> made custom changes that need to be forward-ported. IIUC, this will
>> also mean that the waterfall default page is gone, which might surprise
>> I suppose all slaves also need to upgrade.
> Why is the waterfall default page gone? I had that in my 0.7.9 setup, at
> least. Provided the 0.7.5 slaves work with 0.7.10, then no, it's not
> necessary to upgrade the slaves. The problem in buildbot was strictly
> with the change detection in hg repos (combined with the Mercurial API,
> which hasn't entirely become stable -- so it changed a bit in 1.1).
My understanding is that with 0.7.6 and later, the default page
won't be the waterfall anymore. In the 0.7.6 release notes, it
# The initial page (when you hit the root of the web site) is served
# from index.html, and provides links to the Waterfall as well as the
# other pages.
In the 0.7.9 release notes, it says
# The html.Waterfall status target was replaced by html.WebStatus in
# 0.7.6, and will be removed by 0.8.0.
But then, I have not tried installing it, so I don't know what it
actually looks like.
More information about the Python-Dev