= Welcome to the Boost Trac = == '''IMPORTANT''' This trac is now deprecated, please head over to https://github.com/boostorg and file issues and PR's there instead. == Trac bugs that are still open will be migrated to the github issue tracker for each repository at the discretion of the library maintainer. Please contact the library maintainer via the [https://www.boost.org/community/groups.html#main Boost Developer ML] if you have questions about the policy for a specific library. [[br]] What follows is the archive of the old Trac bug database and Wiki... [[br]][[br]][[br]][[br]] [http://www.boost.org 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: * [BoostSubversion Access the Boost Subversion Repository] * [/newticket Submit patches, bug reports, and feature requests]. Please: - '''[/search?ticket=on search] first''' to avoid creating duplicates. - Use the [/prefs 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 [http://www.boost.org/more/submission_process.htm arise differently]. * [http://svn.boost.org/svnmanager 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 [/prefs 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 [mailto: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 [http://sourceforge.net/tracker/?group_id=7586 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 [/prefs 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 == ~~You can [http://svn.boost.org/trac/boost/browser browse the Boost Subversion repository] online~~ or retrieve Boost via a [http://subversion.tigris.org/ Subversion] client. Most users will be interested in either the stable or the development branch of Boost: * 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: svn up 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 [wiki:ModularBoost '''Documentation for Modular Boost, Git, and the conversion''']. == Guidelines == * [wiki:Guidelines/MaintenanceGuidelines Maintenance Guidelines] * [wiki:Guidelines/WarningsGuidelines Compiler (and other) Warnings - avoiding and/or suppressing them] * [wiki:Guidelines/DoxygenGuidelines Doxygen+Quikbook Limitations and Guidelines] * [wiki:Guidelines/VxWorks Guidelines for using Boost on VxWorks] * [wiki:TravisCoverals Step by step instruction for TravisCI and Coveralls integration] * [wiki:Guidelines/ModerationRejection Canned messages for rejected postings] == Releases == There is a major effort underway to improve Boost Testing and Release practices and procedures. * [https://github.com/boostorg/boost/wiki/Release-Schedule Release Schedule] * [wiki:DeveloperChecklist Developer's Library Maintenance Checklist] * [wiki:SuggestionsForOneDotThirtySix Suggestions for Release 1.36.0] * [wiki:ImprovingPractices Development and Release Practices] * [wiki:ReleasePractices/ManagerCheckList Release Manager's Checklist] * [wiki:ReleasePractices/Procedures Release Procedures for Developers] (needs updating, perhaps merge with Development and Release Practices) * [wiki:ReleasePractices/HotFixes Patches for release specific problems] * [wiki:ReleasePractices/PostBetaMerges Post-beta merge policy] * [https://github.com/boostorg/boost/wiki/Release-Communications Heads up messages to notify developers as deadlines loom] == Review Schedule == * [wiki:ReviewScheduleLibraries Review Schedule Libraries] == Projects == * [wiki:ModuleDepednecies Reducing Modules dependencies] * [wiki:SoC2014 Google Summer of Code (2014)] * [wiki:BoostTransaction Boost.Transaction discussion] * [wiki:SoC2013 Google Summer of Code (2013)] * [wiki:SoC2012 Google Summer of Code (2012)] * [wiki:SoCPrevious Previous Summer of Code Project Ideas] * [wiki:SandboxTemplate Sandbox Template] * [wiki:GraphVersion2 Boost.Graph version 2] * [wiki:IostreamsRoadmap Boost.Iostreams Roadmap] * [wiki:BoostFusion0x Implementing a mini Boost.Fusion in C++0x] * [wiki:BoostPhoenix3 Phoenix Reloaded (a.k.a. Boost.Phoenix v3)] * [wiki:BoostMplRoadmap Boost.MPL Roadmap] * [wiki:LibrariesUnderConstruction Libraries Under Construction] * [wiki:WarningFixes Reducing the number and impact of compiler warnings from Boost code.] * [wiki:DebuggerVisualizers Debugger Visualizers for the Visual Studio IDE] * [wiki:BoostEvo Draft policy for Boost library evolution] (Was Boost 2.0) == Infrastructure == * [wiki:testing Testing] * [wiki:website Web Site] * [wiki:CMake CMake] * [wiki:BoostDocs/GettingStarted Getting Started with Boost Docs] * [wiki:BoostDocs/PDF PDF Build of Boost Documentation] * [wiki:ImprovingBoostDocs Improving Boost Docs] * [wiki:BoostTools Information relating to Boost Tools] * [wiki:HeaderModularization Header Modularization] * [wiki:BugSprintJune2009 June 2009 Bug Sprint] * [wiki:CommunityMaintenance Community Maintenance Guidelines] == Platform Champions == [wiki:PlatformChampions Platform Champions] are experts that Developers can turn to when they have a problem with a particular compiler or operating system. == References == [wiki:References] contains pointers to books or papers about Boost. == People == Go to the [wiki:People people page]. It has very few entries at the moment, please add yourself. == Donations == Donate to the [wiki:StudentFundDonations Boost student fund] here.