| | 1 | The Boost Bug Sprint is modeled on the Ubuntu bug sprints. |
| | 2 | The idea is to focus on dealing with Trac tickets (bugs, feature requests, tasks, etc) for a short period of time, and reduce the number of open issues dramatically. |
| | 3 | |
| | 4 | Here is a description of the [TicketWorkflow ticket work flow]. |
| | 5 | |
| | 6 | The boost bug sprint starts Saturday, November 27, 2010 and runs through Sunday December 5th. |
| | 7 | |
| | 8 | What can you do? |
| | 9 | |
| | 10 | == You can fix bugs == |
| | 11 | * If you are a library maintainer, you can commit your fixes. |
| | 12 | * 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. |
| | 13 | |
| | 14 | == You can characterize bugs == |
| | 15 | * 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. |
| | 16 | * You can write test cases demonstrating the problem, and attach them to the Trac ticket. |
| | 17 | * 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." |
| | 18 | |
| | 19 | == You can test patches == |
| | 20 | * 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." |
| | 21 | * You can write test cases for the patches, and attach them to the ticket. |
| | 22 | |
| | 23 | == You can help implement new features == |
| | 24 | * 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!!). |
| | 25 | |
| | 26 | == You can write new tickets === |
| | 27 | * If you find a problem with a library, you can write up a new ticket. Please include a test case, and a description of your system/compiler/etc. |
| | 28 | |
