Changes between Version 15 and Version 16 of TicketWorkflow


Ignore:
Timestamp:
Nov 2, 2010, 4:40:36 PM (8 years ago)
Author:
Marshall Clow
Comment:

Added section on creating tickets

Legend:

Unmodified
Added
Removed
Modified
  • TicketWorkflow

    v15 v16  
     1= How to Create Boost Tickets =
     2If (heaven forfend) you find a problem in Boost, the best way to get it noticed is to file a Trac ticket. Posting on the mailing lists is great for getting attention, but things get lost there.
     3
     4'''When creating a ticket, make sure that you do the following:'''
     5   * Set your email address in "preferences" first. Almost certainly, the author of the library will ask you for more information. If you don't include an email address, there is no way to contact you.
     6   * Indicate the version of boost that you are using, along with the OS/compiler combination. If you are using any custom libraries as well (STLPort, say), please mention them.
     7   * If you know the maintainer of the library that you are submitting the ticket against, please set the ''owner''. Here is a [report:15 list of maintainers].
     8
     9* '''Choose the bug type carefully''':
     10   * ''Bugs'' - something that should work doesn't.
     11   * ''Feature Request'' - something that you think the library should do, but it currently does not.
     12   * ''Patches'' - Please don't use the "Patches" bug type. If you have a patch, that's great. Attach it. But mark the ticket as either a "bug" or "feature request".
     13   * ''Support Requests'' - another unused ticket type. Support is better handled on the mailing list.
     14   * ''Library Submission'' - if you have a library to submit, contact the review manangers to arrange a review.
     15   * ''Tasks'' - rarely used, mostly by library maintainers to make sure they don't forget something.
     16
     17* '''Severity - how bad is this ticket?'''
     18   * ''Showstopper'' - this problem is so bad, that we should hold up a release if it's not fixed. Note that the release managers and/or the library maintainers may have different opinions.
     19   * ''Regression'' - something used to work (in a previous release), but no longer does.
     20   * ''Problem'' - the default value.
     21   * ''Optimization'' - this makes the library work better (usually with a patch enclosed).
     22   * ''Cosmetic'' - minor problems, like using the wrong "they're/there/their" in a comment, or a typo in the documentation. Do not be discouraged from creating tickets for "minor" issues like this. They're easy to fix, and they make boost better.
     23
     24
    125= How to Handle Boost Tickets =
    226