>> >Date-Time Change History is missing
>>
>> It isn't in CVS either. And if it isn't in CVS, it doesn't go in the
>> release. The release is really just an export of CVS as of
>> the release tag.
>> Nothing gets added, nothing gets subtracted.
>>
>> --Beman
>
>My point is: shouldn't we check it before release, so that library authors
>will take care about it. It least links on front page.
>Didn't we have an utility for that?
Yes - See http://www.boost.org/tools/inspect/index.html. Bjorn Karlsson runs it and then pesters people to fix the problems.
Maybe we should run it daily and post the output with the regression tests. Perhaps if it was public developers would be more motivated to fix problems.
Hum... I just had a thought. What if the output was reformatted as an html table? One row per library with columns for the error counts for the different kinds of errors. Click through to see the actual error messages.
That would give us an overview we could watch as we approached releases.
Anyone like to volunteer to write such a program? It should probably be separate from inspect itself to separate the concern of detecting errors separate from reporting concerns.
Thoughts?
--Beman
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
