Currently http://subversion.apache.org/buildbot contains a mixture of
builds for all active branches (trunk, 1.6.x, 1.7.x). That makes it
unfeasible to track the status of, say, the 1.6.x branch (which had
a failure tonight - but that will be washed out soon by trunk commits
and 1.7.x backport merges).
We could split up each builder ("column" in
http://subversion.apache.org/buildbot) into N builders, one per branch
--- that adds no maintenance overhead (according to Gavin), and will
allow us to easily monitor the status (and history) of each branch
by adding a http://subversion.apache.org/buildbot-17x redirect that
shows only the 1.7.x builders (at least N recent builds of each).
WDYT?
Daniel
(Implementation-wise --- see mkcassbuilder() in cassandra.conf for an
example.)
