I&#39;m responsible for maintaining the local Boost install for a large group of developers, and I find myself spending an inordinate amount of time reapplying our local patches for Boost bugs every time a new version comes out, seemingly with no end in sight. One obvious example is <a href="https://svn.boost.org/trac/boost/ticket/3645" target="_blank">https://svn.boost.org/trac/boost/ticket/3645</a>: the report is clear and specific, documents a real bug, and provides a trivial patch which completely resolves the issue. It&#39;s everything one could possibly want in a bug report, and it has been utterly ignored for over a year. In my experience this has been the rule rather than the exception; other examples that I&#39;ve been personally acquainted with include <a href="http://lists.boost.org/Archives/boost/2009/06/153214.php" target="_blank">http://lists.boost.org/Archives/boost/2009/06/153214.php</a>, <a href="https://svn.boost.org/trac/boost/ticket/4918" target="_blank">https://svn.boost.org/trac/boost/ticket/4918</a>, and <a href="https://svn.boost.org/trac/boost/ticket/4919" target="_blank">https://svn.boost.org/trac/boost/ticket/4919</a>. In every case the reporters have done everything they could to provide a useful bug report, up to and including providing patches, but have been met with profound silence.<div>

<br></div><div>Does anyone have any suggestions for how to get action in these situations?</div>