Welcome to the Boost Trac
Boost is a collection of free, peer-reviewed C++ libraries. This Trac is used to aid in the development of Boost, by tracking software issues, documenting Boost development procedures, and providing navigation aids to the Boost source code repository. From this Trac, you can:
- Access the Boost Subversion Repository
- Submit patches, bug reports, and feature requests. Please:
- search first to avoid creating duplicates.
- Use the Preferences link at the top of this page to let us know your email address even if you don't have a Trac userid. Otherwise we won't be able to follow up with you about your bug report.
- Do not suggest features unless you can identify a particular Boost library in which they belong—new libraries arise differently.
- Change your Subversion password
Getting a Trac/SVN Userid
If you are just submitting bug reports, you probably don't need a Trac userid, but please use the Preferences link at the top of this page to enter your email address before submitting your report. Unless you take this step, we won't be able to follow up with you about your issue (and we often need more information in order to do anything useful with a report) and you won't be notified of progress or changes to its status.
Trac userids can be had on request by sending email to boost-owner-AT-lists.boost.org describing your role. Userids are normally granted to maintainers and authors of prospective (“sandbox”) and accepted Boost libraries, people working on the Boost website, and people contributing significant content to this Wiki.
If your request for a userid is granted you'll receive an invitation to register from “SVNManager” and you'll have total freedom to choose your new userid and password. If your role includes Subversion access your SVN userid and pasword will be the same as your Trac userid and password. Please:
- if you had a SourceForge userid and Boost tickets were assigned to you on the old SourceForge trackers, either pick the same userid or reassign all your tickets imported from SourceForge to your new userid as described in TicketWorkflow.
- choose a userid that is easily identified as you (e.g. use your full name)!
- use the Preferences link at the top of this page to enter your email address. Unless you take this step, tickets can't be assigned to you and any bugs you report will appear to be from an unreachable anonymous user.
- read TicketWorkflow
Quick Access to the Boost Subversion Repository
- The development branch is available at http://svn.boost.org/svn/boost/trunk
- The sandbox is available at http://svn.boost.org/svn/boost/sandbox
To check out the Boost development trunk using the command-line Subversion tool, svn, use:
svn co http://svn.boost.org/svn/boost/trunk boost-trunk
At any time, you can update your Boost development branch (which now lives in boost-trunk) with:
Please refer to BoostSubversion for more information about the Boost Subversion repository.
Git and Modular Boost
Boost is moving from Subversion centralized version control to Git distributed modular version control. See ''Documentation for Modular Boost, Git, and the conversion''.
- Maintenance Guidelines
- Compiler (and other) Warnings - avoiding and/or suppressing them
- Doxygen+Quikbook Limitations and Guidelines
- Guidelines for using Boost on VxWorks
- Step by step instruction for TravisCI and Coveralls integration
- Canned messages for rejected postings
There is a major effort underway to improve Boost Testing and Release practices and procedures.
- Release Schedule
- Developer's Library Maintenance Checklist
- Suggestions for Release 1.36.0
- Development and Release Practices
- Release Manager's Checklist
- Release Procedures for Developers (needs updating, perhaps merge with Development and Release Practices)
- Patches for release specific problems
- Post-beta merge policy
- Heads up messages to notify developers as deadlines loom
- Reducing Modules dependencies
- Google Summer of Code (2014)
- Boost.Transaction discussion
- Google Summer of Code (2013)
- Google Summer of Code (2012)
- Previous Summer of Code Project Ideas
- Sandbox Template
- Boost.Graph version 2
- Boost.Iostreams Roadmap
- Implementing a mini Boost.Fusion in C++0x
- Phoenix Reloaded (a.k.a. Boost.Phoenix v3)
- Boost.MPL Roadmap
- Libraries Under Construction
- Reducing the number and impact of compiler warnings from Boost code.
- Debugger Visualizers for the Visual Studio IDE
- Draft policy for Boost library evolution (Was Boost 2.0)
- Web Site
- Getting Started with Boost Docs
- PDF Build of Boost Documentation
- Improving Boost Docs
- Information relating to Boost Tools
- Header Modularization
- June 2009 Bug Sprint
- Community Maintenance Guidelines
Platform Champions are experts that Developers can turn to when they have a problem with a particular compiler or operating system.
References contains pointers to books or papers about Boost.
Go to the people page. It has very few entries at the moment, please add yourself.
Donate to the Boost student fund here.