There were only 13 changes to the trac database yesterday. [ I'd like to say "13 tickets were changed", but some tickets were changed more than once. ] The decrease in activity continues. It's time to ramp it up - there are only three more days in the Bug Sprint. In the last bug sprint, we closed almost 200 tickets (not 100 - I misremembered). So far this time, we're down a (net) 13 tickets from the start of the sprint! If you think it's too late to get involved - you're wrong! If you're looking for things to do, there are several patches for Date-Time waiting to be reviewed (thx to ktchan): #2956 is very old and need review #3651 is simple documentation changes #4057 appears at a glance simple changes #4411 & #4754 is simple update to time zone data file #4475 #4798 is a simple change #4845 is simple documentation changes #4870 #4920 is simple update to date_time examples and there are a bunch of program-options bugs that can be looked at: #850 program_options strips off escaped quotes in some situations #1132 zero_tokens doesn't work #3813 program_options::options_description.add() permits duplicate options #3909 parse_command_line has bad declaration #3992 Example in documentation for program_options doesn't compil #4040 Program Options has issues with options that support multiple tokens when using multiple parsers #4133 std::logic_error as a base class for program_options::error #4137 boost::program_options::value_semantic missing 's' at the end #4149 exceptions thrown by typed_value::default_value() are not documented #4150 bool_switch() is exception-unsafe #4151 option_description::option_description(3 args) is exception-unsafe #4267 validation_error documentation #4469 Bugs in program_options implementation #4510 [program_options]: implicit_value and positional options conflict #4597 options_description should be defined as noncopyable #4656 program_options parse_config_file() set iostream failbit even if the parse result is ok #4858 Documentation error - Responsefile example code can crash (You all know the drill: develop a fix, test it locally, make a patch, attach it to the ticket) A couple of notes: 1) Please log into the Trac system before you add/modify a ticket. "Anonymous said:" is hard to follow up. 2) It is perfectly OK to add a comment to a ticket that says "I tested this patch on my system (foo, gcc 1.2.3.4, etc) and it worked fine/didn't work/etc" General information about the bug sprint is here: https://svn.boost.org/trac/boost/wiki/BugSprintNov2010 General information about how the Trac system works is here: https://svn.boost.org/trac/boost/wiki/TicketWorkflow Overall bug count: November 26: 946 November 27: 939 November 28: 930 November 29: 934 (whoops, that's the wrong direction!) November 30: 931 (better, but the delta is too small) December 1: 929 December 2: 930 December 3: 933 (ouch!) Activities on the trac system yesterday: jim.bell@ 4 viboes 2 jaredgrubb@ 2 --others-- 5 Useful reports: https://svn.boost.org/trac/boost/report/1 -- full list of tickets https://svn.boost.org/trac/boost/report/18 -- ticket counts by owner https://svn.boost.org/trac/boost/report/19 -- ticket counts by component https://svn.boost.org/trac/boost/report/20 -- ticket counts by ticket type https://svn.boost.org/trac/boost/report/21 -- ticket counts by milestone