[Bug Sprint] Status for Thursday, December 2nd
There were 33 changes to the trac database yesterday. [ I'd like to say "33 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 four more days in the Bug Sprint. In the last bug sprint, we closed almost 100 tickets. So far this time, we've closed 16. 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 Activities on the trac system yesterday: bemandawes 7 ktchan 4 jim.bell@ 4 --others-- 18 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
Marshall Clow-2 wrote:
In the last bug sprint, we closed almost 100 tickets. So far this time, we've closed 16.
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
I will add that there were at least 23 tickets created, so there are at least 39 tickets that have been closed during the Bug Sprint. I sent 9 tickets for Boost.Thread that could be integrated and closed easily. Best, Vicente -- View this message in context: http://boost.2283326.n4.nabble.com/Bug-Sprint-Status-for-Thursday-December-2... Sent from the Boost - Dev mailing list archive at Nabble.com.
On Dec 2, 2010, at 8:23 AM, Vicente Botet wrote:
Marshall Clow-2 wrote:
In the last bug sprint, we closed almost 100 tickets. So far this time, we've closed 16.
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
I will add that there were at least 23 tickets created, so there are at least 39 tickets that have been closed during the Bug Sprint.
True - I was speaking imprecisely. In the last bug sprint, we started with 989 open tickets, and finished with 789. That's a (net) change of 200 open tickets - but, as you say, it's really more than that, since there were tickets opened during the sprint.
I sent 9 tickets for Boost.Thread that could be integrated and closed easily.
Cool. Let's make it so. ;-) -- Marshall
Was: Re: [boost] [Bug Sprint] Status for Thursday, December 2nd On 1:59 PM, Marshall Clow wrote:
[...]
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
This is for someone with trunk commit access, right? ***This is where I want to be a fly on the wall.*** ktchan: you took a look at these and determined they're "low-hanging fruit", right? (Thanks, btw!) So, when someone looks to actually patch and commit, could you also... 1. Jot a little note for each -- your level confidence that it's right, and/or why you'd hesitate to commit. (Just one sentence.) 2. Keep track of how long it takes you to work through them. ... and publish this to this mailing list.
On 02/12/2010 17:02, Jim Bell wrote:
Was: Re: [boost] [Bug Sprint] Status for Thursday, December 2nd
On 1:59 PM, Marshall Clow wrote:
[...]
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
This is for someone with trunk commit access, right?
***This is where I want to be a fly on the wall.***
ktchan: you took a look at these and determined they're "low-hanging fruit", right? (Thanks, btw!)
Well, the 6 tickets with the words "is (a) simple" in my description yeah. Only one of those is actual library code changes explicitly null initialising couple of variables so valgrind doesn't warn. The other 5 are either examples or update to the time zone data file. The remaining do need review because they're either patches to non-regression tested system or consideration need to be given to any unintended side effects. KTC
On Thu, 2010-12-02 at 20:26 +0200, KTC wrote:
Well, the 6 tickets with the words "is (a) simple" in my description yeah. Only one of those is actual library code changes explicitly null initialising couple of variables so valgrind doesn't warn. The other 5 are either examples or update to the time zone data file.
Damned, I forgot all about this one. We use the geonames database and found zones not listed by the boost date_time library. I made the necessary updates, but unfortunately I forgot to report them to boost. Simply providing our current file might be of some help to anyone attacking the problem. I made the file temporarily available at http://weather.weatherproof.fi/date_time_zonespec.csv According to my cvs commits, I failed to define Argentinian zones (America/Argentina/*) properly, the DST information is missing. I cannot remember why I failed to define the zones properly. All other updates I made should be correct according to my commit messages. Our file is dated June 13th 2009, so any TZ changes after that have not made it into our db. The changes were made to boost 1.37 db. I hope the file is at least somewhat useful. --> Mika Heiskanen
participants (5)
-
Jim Bell -
KTC -
Marshall Clow -
Mika Heiskanen -
Vicente Botet