On Sun, Jan 26, 2014 at 6:17 PM, Marshall Clow
I’ve put up a set of procedures for the Boost Community Maintenance Team (CMT) on the wiki at: https://svn.boost.org/trac/boost/wiki/CommunityMaintenance
Comments welcomed.
The CMT will operate on a "propose and review" process, where a change goes through the following phases. 1. Someone decides to work on a bug/test failure/etc and announces this on the mailing list. Will the CMT have it's own mailing list or use boost-devel? In the case of a separate mailing list, you should add it to Boost's mailing list web page and have a link to it. If it's going to be boost-devel, we should probably have a standardized subject line tag to make it easy to filter out the non-CMT related mail, e.g. [boost][cmt] <subject line> or maybe just use the CMT libraries name, e.g. [boost][signals] <subject line> or maybe a combination, e.g. [boost][cmt][signals] <subject line> 1. Discussion may ensue on the ML about the best way to proceed. 2. The code/tests/docs are developed and a pull request is made (on the list). 3. The request is reviewed by other members of the list. (repeat steps 3 and 4 as necessary) 4. The request is committed to the "develop" branch by a CMT manager who notifies the person who made the pull request. Just to close the loop... 1. The person who made the pull request is responsible for verifying all the tests passed, and notifying the CMT manager when it is ready to be merged to "master"
— Marshall
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost