On Tue, Apr 22, 2014 at 2:08 PM, Edward Diener
On 4/22/2014 12:29 PM, Ben Pope wrote:
In case you haven't heard of the CMT: https://svn.boost.org/trac/boost/wiki/CommunityMaintenance
I'm also interested in getting the test results less yellow and more green, I don't have a lot of time, I'm sure I'm not alone.
There are quite a few places where the library code is probably fine, but the failure is in the test itself, the fix is often simple and uncontroversial.
Without picking on any particular library or author, here are some examples:
* Link the tests with boost::system http://thread.gmane.org/gmane.comp.lib.boost.maint/92 * Merge existing fixes in develop to master http://thread.gmane.org/gmane.comp.lib.boost.devel/250129 * Fight with casts http://thread.gmane.org/gmane.comp.lib.boost.devel/250143 * Disambiguate a type https://svn.boost.org/trac/boost/ticket/9540
These refer to system, MPI, utility, and assign. None of these are in the list of libraries which the community maintenance team has write acces to apply fixes.
Right.
Hopefully the developers who do have write access to these libraries will look at the issues involved.
Right, but what we are now saying is that if the maintainers for those libraries don't respond, the submitters can ask on the CMT mailing list ( http://lists.boost.org/mailman/listinfo.cgi/boost-maint) for a response. The CMT may concentrate on pull requests initially, but as they gear up then other forms of support requests will be dealt with by the CMT but only when there is no response from a library maintainer. --Beman