The boost bug sprint started Friday, May 29th, and runs through Sunday June 7th. We've only got two more days - keep up the good work! 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. 6:00 AM PDT 5/31: 761 open tickets. 6:00 AM PDT 6/2: 747 open tickets. 6:00 AM PDT 6/3: 748 open tickets. 6:00 AM PDT 6/4: 739 open tickets. 8:00 AM PDT 6/5: 730 open tickets. 7:00 AM PDT 6/6: 719 open tickets. Activity: 5/29: 6 new tickets, 77 modifications, 25 tickets closed 5/30: 2 new tickets, 42 modifications, 17 tickets closed 5/31: 2 new tickets, 27 modifications, 8 tickets closed 6/1: 2 new tickets, 42 modifications, 17 tickets closed 6/2: 5 new tickets, 18 modifications, 5 tickets closed. 6/3: 4 new tickets, 19 modifications, 2 tickets closed. 6/4: 3 new tickets, 42 modifications, 24 tickets closed. 6/5: 3 new tickets, 35 modifications, 8 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. Also, tickets can be closed and reopened. ] What can you do? See <https://svn.boost.org/trac/boost/wiki/BugSprintJune2009> for details. I've added four 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> There's been a lot of discussion on the list about tickets; and there are about a dozen patches that have been tested and are ready to be applied. If you're looking to help, you can look at some of the older bugs, say, the ones for Boost 1.36, and determine if they still apply. If they do, note that in the ticket. There are 35 tickets that are still open that are marked as "to be fixed in Boost 1.36" See <https://svn.boost.org/trac/boost/report/3> for a list of open tickets by milestone. --------- 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 I consider this Feature Requests unrelated to any Boost library. It shuld be added to the library wish lists. Could we close it? Vicente Ticket #1777 (new Feature Requests) Opened 14 months ago Last modified 14 months ago provide md5 Reported by:Erik <esigra@.>Owned by: Milestone: Component: None Version: Severity: Not Applicable Keywords: md5 Cc: There are some threads in the mailing list archive about providing boost::md5 but it did not seem to lead anywhere yet. It would be useful for a project that I work on. We maintain a fork of md5 in our source tree and since we already depend on boost it would be great to get rid of our fork and use boost instead for our md5 needs. I suppose this may apply to other projects as well. All interested parties can subscribe to this ticket to track the progress of this issue.
Hi, Is this tools/litre official? If not, couldn't we close this ticket? Ticket #1479 (new Tasks) Opened 19 months ago Document litre tool. Reported by:grafikOwned by: Milestone: To Be Determined Component: None Version: Boost Development Trunk Severity: Cosmetic Keywords: tools litre Cc: Add documentation, and copyrights, for the code at tools/litre. Could use a general cleanup into build/src/doc/example structure.
vicente.botet wrote:
Hi, Is this tools/litre official? If not, couldn't we close this ticket?
Not being official is not an excuse to avoid documentation. The tools is used by some people.
Ticket #1479 (new Tasks) Opened 19 months ago Document litre tool. Reported by:grafikOwned by: Milestone: To Be Determined Component: None Version: Boost Development Trunk Severity: Cosmetic Keywords: tools litre Cc:
Add documentation, and copyrights, for the code at tools/litre. Could use a general cleanup into build/src/doc/example structure.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
participants (3)
-
Marshall Clow -
Rene Rivera -
vicente.botet