Subject: [Boost-docs] Making Boost Doc builds more robust
From: Beman Dawes (bdawes_at_[hidden])
Date: 2008-12-01 16:55:39
Right now the Boost documentation build is a serious problem from the
standpoint of release management.
There is no way to tell if doc builds are working other than asking
people to look at the results. This prevents automatic notification if
the build process breaks. It seems to me the first step in making doc
builds more robust is adding a boost-root/doc/test directory with a
Jamfile and test cases that can be used to debug the problems.
Documentation builds only work for me on Linux. Builds on Windows work
for Eric, IIUC, but not for me. This prevents me from running automatic
daily release branch builds. It would be a lot easier to debug this
problem if we had a test setup.
Once we have a test setup that can detect if an error occurs, we can
work on ensuring that error messages (1) say what probem occurred and
(2) say what to do to correct the problem.
This archive was generated by hypermail 2.1.7 : 2017-11-11 08:50:40 UTC