- Supply more builds to the Cdash dashboard at
http://www.riverace.com/CDash-1.4.2/index.php?project=qpid-cpp - I
have a RHEL 5 and a Windows XP build there now. The dashboard is
driven by outputs from the Cmake build - it makes it very easy to
watch the trends, note where tests are failing, make some estimation
of what changes caused the problems and who made them, etc. Getting
all the build and regression info in one place goes a long way toward
helping the entire development crew keep an eye on things. If having
this hosted at riverace.com is a problem, I'm available to help
migrate it to qpid.apache.org.
I don't have an issue it being at riverace.com, however if you want to
ask on #asfinfra they
might be fine with us running it qpid.apache.org. They will however
require it be all OS
licensed or something like that. if it is not, we use ptol, which is
built using qpid which could
also be setup at apache if there is interest.
The advantage of having it run at apache.org is that more people can
setup and maintain
test profiles, currently I see 4 profiles red on our trunk build system.
- Set a deadline for transition to Cmake and deletion of the autoconf
files. I understand the fact that for Linux developers, the path of
least resistance is to stick with what's known. Therefore, some hard
goal is probably what will be needed to make the transition.
From what I can see CMake is coming along well. I don't think autotools
can be removed at
the 0-6 release, as we should give enough time for the upstream and
downstream projects to
update themselves. We probably need to get two or three releases out
with CMake, so I would
think knowing all is good and ready to remove autotool would most likely
be sometime
around spring.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
