The boost bug sprint starts today Friday, May 29th, and runs through
Sunday June 7th.
Status
5/29: 812 open tickets.
The goal is to address a large number of open bugs/patches/feature
requests in the Trac system at http://svn.boost.org/trac/report/1.
There are currently 812 open tickets; we'd like to knock that number
down _a lot_.
What can you do?
1) You can fix bugs.
* If you are a library maintainer, you can commit your fixes. ;-)
* If you are not a library maintainer, you can fix a problem on your
local machine (and test it!!), and then attach your fix as a patch to
the Trac ticket for the library maintainer to commit. If you do this,
please provide a test case that exercises the problem; i.e, one that
fails w/o your patch, and succeeds afterwards.
2) You can characterize bugs.
* You can attempt to replicate the bug on your system(s), and attach
information that you discover to the Trac ticket. This will make it
easier for other people to solve the problem, even if you cannot.
* You can write test cases demonstrating the problem, and attach them
to the Trac ticket.
* You can determine if the bug still exists; sometimes they get
fixed, and the ticket never gets closed. In this case, try to
identify a checkin that addresses the bug; it's always suspicious
when bugs go away "by accident."
3) You can test patches.
* Some of the tickets in the Trac system contain patches - some are
quite old. You can install these patches on your system, and
determine if they (a) build, and (b) work. If you do this, please
provide detail. Don't just say "works for me" - say "I installed this
over revision XXX on system YYY with compiler ZZZ. The patch
installed and compiled successfully, and passed all the tests."
* You can write test cases for the patches, and attach them to the ticket.
4) You can help implement new features.
* There are a whole set of "feature requests" in the Trac system. If
you have an idea about one of these, you can add comments to the Trac
system. You can attempt to implement these new features, and attach
the patch to the ticket. (Don't forget the test cases!!).
Every day during the bug sprint, I'll post the # of tickets
modified/closed/opened on the previous day, as well as the total
number of open tickets.
If you aren't sure where to start, you can verify existing patches.
Here are a list of patches that have been open at least six months.
[ Note: The URL for ticket number XXXX is
https://svn.boost.org/trac/boost/ticket/XXXX ]
Bug # Library Description
2603 smart_ptr patch for owner_before and owner_less support
with shared_ptr/weak_ptr
2581 mpi MPI tutorial sample has missing includes
2509 string_algo case conversion (to_upper) fails in Codegear
C++Builder 5.9.3
2484 bimap Const-overload needed for bimap
associative_container_adaptor::count()
2482 concept_check msvc-9.0 unreferenced formal parameter
warning when using boost::breadth_first_visit
2454 fusion Fusion - MSVC level 1 warnings
2452 fusion Fusion vector warning 4512 supression would be nice,
2390 test "[patch] fix gcc-4.3 ""unused"" warning in
floating_point_comparison"
2370 lexical_cast [lexical_cast] Patch to reduce warnings for
CodeGear (Borland)
2351 spirit Minor BOOST_SPIRIT_RULE fixes (rule_parser.hpp)
2312 smart_ptr intrusive_ptr::operator= should have by-value argument
2304 spirit Patch to fix warnings in spirit
2297 mpl Workaround for GCC bug
2290 serialization Patch for GCC-4.0.1 compatibility (and better
compile time).
2271 serialization Cannot load version 1.35.0 xml archives that
contain vectors of primitive types
2208 Python Pyste can use ElementTree from Python 2.5
2149 date_time Updated Daylight Savings Time for Australia/Perth
2142 Python Patch for boost.python - return_pointee_value,
2114 none Patch for export symbols from shared library
2064 tokenizer Interval notation is wrong in tokenizer documentation
2053 threads porting boost to avr32 linux platform
1947 iterator traversal access decoupling
1861 date_time time_duration type can not be correctly
written or read of the period spans 24 hours of more (vc9 and
probably others).
1850 thread request for unlock_guard (and/or unique_unlock) to
compliment lock_guard/unique_lock
1811 Building Boost Help packaging by supporting DESTDIR
1791 lexical_cast fix warning on MSVC warning level 4
1702 random serialization for Mersenne twister
1681 filesystem patch for NTFS symbolic links
1541 parameter [parameter] Patch for missing includes
1535 function [result_of] remove unneeded headers
1534 build Add support for winsdk 6.1.6000 to Boost.Build.v2
1533 iterator boost/function.hpp unneeded in transform_iterator.hpp
1529 fusion Missing include statement
1521 bimap Missing #include statements
1519 iterator lvalue-ness resurrection in transform_iterator
1437 random "normal_distribution.hpp, improvements to
distribution and possibly speed"
1418 serialization polymorphic archive performance improvement
1377 GIL Add ability to save RGBA image as TIFF with
associated-alpha (premultiplied) transparency channel.
1341 asio unused argument and another g++ warning
1338 numeric g++ warnings and incomplete header inclusions
1271 Python unused parameter warning in release build
1116 build disable some warnings in msvc build
1066 Python Patch to make Boost.Python compile on SunCC
1049 mpl Getting mpl/has_xxx.hpp to compile on AIX
1020 iterator Boost.Iterator proposal to add is_constant_iterator
903 Python inconsistent usage of function pointer typedefs
868 thread [thread] thread_specific_ptr::element_type ?
864 lambda [lambda][utility] Make lambda support result<>
863 [parameter] fix operator|| for lazy binding
861 parameter Detect nested template members with
has_template_xxx,mpl
857 Python add shared_ptr< const T> support
827 date_time Unused variable in format date parser,
802 thread [thread] MSVS: Allow use of thread headers with /Za
761 mpl [mpl] evc4 port
717 Python Add operator for __repr__ similar to __str__
637 mpl Adjusts mpl::pair concept to be compatible with STL pairs
--------- 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"