Bug Sprint Report for Friday, May 29th

The boost bug sprint started Friday, May 29th, and runs through Sunday June 7th. We're off to a great start! Status <https://svn.boost.org/trac/boost/report/1> 7:00 AM PDT 5/29: 797 open tickets. 7:45 AM PDT 5/30: 772 open tickets. Activity: 5/29: 6 new tickets, 77 modifications, 25 tickets closed [ Numbers may not add up because I am counting via two different methods, using data that is time-stamped in two different time zones ] What can you do? See <https://svn.boost.org/trac/boost/wiki/BugSprintJune2009> for details. I've added three new reports to the trac: Open ticket count by owner: <https://svn.boost.org/trac/boost/report/18> Open ticket count by component: <https://svn.boost.org/trac/boost/report/19> Open ticket count by ticket type: <https://svn.boost.org/trac/boost/report/20> Open ticket count by milestone: <https://svn.boost.org/trac/boost/report/21> The following bugs appear to have been fixed, but the tickets were never closed. I would appreciate it if the library maintainers could verify this and close the tickets. https://svn.boost.org/trac/boost/ticket/145 Iterator https://svn.boost.org/trac/boost/ticket/287 date_time The following tickets are feature requests that are unlikely ever to be implemented. Should they be closed? https://svn.boost.org/trac/boost/ticket/558 database https://svn.boost.org/trac/boost/ticket/100 concept_check https://svn.boost.org/trac/boost/ticket/182 concept_check --------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou@u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost@objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco@osl.iu.edu> (will test and commit graph patches) 7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4) 9) Steven Watanabe <watanabesj@gmail.com> (bug fixes, como) 10) vicente.botet" <vicente.botet@wanadoo.fr> 11) Stjepan Rajko <stjepan.rajko@gmail.com> (fusion) 12) Daniel Wallin (parameter, ...) -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

Hi, Shouldn't we have a ticket status that states feedback for more information from the reporter? IMO the feedback ticktes shouldn't be counted as active from the developper point of view. Vicente

on Sat May 30 2009, "vicente.botet" <vicente.botet-AT-wanadoo.fr> wrote:
Hi,
Shouldn't we have a ticket status that states feedback for more information from the reporter? IMO the feedback ticktes shouldn't be counted as active from the developper point of view.
I think that's a great idea. -- Dave Abrahams BoostPro Computing http://www.boostpro.com

on Sat May 30 2009, "vicente.botet" <vicente.botet-AT-wanadoo.fr> wrote:
Hi,
Shouldn't we have a ticket status that states feedback for more information from the reporter? IMO the feedback ticktes shouldn't be counted as active from the developper point of view.
Does this describe the workflow you're thinking of? http://trac.edgewall.org/wiki/WorkFlow/Examples#OpenSourceopensource-workflo... https://svn.boost.org/trac/boost/wiki/TracWorkflow describes the configuration of this Trac feature. It would be fantastic if you'd like to work out a proposal for Boost! -- Dave Abrahams BoostPro Computing http://www.boostpro.com
participants (3)
-
David Abrahams
-
Marshall Clow
-
vicente.botet