Changes between Version 9 and Version 10 of TicketWorkflow


Ignore:
Timestamp:
Jul 6, 2007, 12:20:36 PM (15 years ago)
Author:
Dave Abrahams
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TicketWorkflow

    v9 v10  
    1 [[PageOutline]]
    21= How to Handle Boost Tickets =
    32
    4 As of this writing, Boost has ''lots'' of open tickets, almost all of which were transferred to our Trac automatedly from !SourceForge.  Here are some effective ways of handling them.
     3As of this writing, Boost has ''lots'' of open tickets, almost all of which were transferred to our Trac automatedly from !SourceForge.  Here are some effective things you can do to help close them.
    54
    6 == Put the Reporter on the Notification List ==
     5 * '''Make sure tickets can be assigned to you''': Tickets cannot be assigned to you unless:
     6   a. you have an account that lets you log into this trac and gives you write access to our Subversion repository.  Send email to boost-owner@lists.boost.org to get an invitation
     7   b. you have entered your email address in Trac (see the “settings“ link that appears in the upper right of this page once you've logged in).
     8 
     9 * '''Get the Reporter on the Notification List''': the ticket reporter's name is a !SourceForge userid.  You can keep that person abreast of developments by adding `@users.sf.net` to the userid—then they'll get emails about all changes to the ticket. 
    710
    8 The ticket reporter's name is a !SourceForge userid.  You can keep that person abreast of developments by adding `@users.sf.net` to the userid—then they'll get emails about all changes to the ticket. 
     11 * '''Move attachments over from !SourceForge'''.  Unfortunately when the tickets were moved over from !SourceForge, attachments were not moved with them.  You can find the old tickets [http://sourceforge.net/search/?group_id=7586&words=dave&type_of_search=artifact&pmode=0&words=&Search=Search here], download the attachments, and attach them to the Trac tickets.  Having a complete record is important to Boost's integrity!
    912
    10 == Move attachments over from !SourceForge ==
     13 * '''Fix the Bugs that are Assigned to You'''. (Duh!) If you're logged in, [report:9 here they are], in order of decreasing priority.
     14 However, if your !SourceForge UserID is not the same as your Trac UserID, you may have a whole slew of other open tickets.  See [report:12 this report] for all the owned tickets sorted by their original owner IDs.
    1115
    12 Unfortunately when the tickets were moved over from !SourceForge, attachments were not moved with them.  You can find the old tickets [http://sourceforge.net/search/?group_id=7586&words=dave&type_of_search=artifact&pmode=0&words=&Search=Search here], download the attachments, and attach them to the Trac tickets.  Having a complete record is important to Boost's integrity!
    13 
    14 == Fix the Bugs that are Assigned to You ==
    15 
    16 (Duh!) If you're logged in, [report:9 here they are], in order of decreasing priority.
    17 However, if your !SourceForge UserID is not the same as your Trac UserID, you may have a whole slew of other open tickets.  See [report:12 this report] for all the owned tickets sorted by their original owner IDs.
    18 
    19 == Triage Unassigned Tickets ==
    20 
    21 report:10 shows all tickets that haven't been assigned to real developers.
    22 
    23 === Assign Component and Owner ===
    24 
    25 The most obvious thing you can do is to set the ticket's “component” field to the right library and assign the ticket to the maintainer of that library.  If the right library doesn't appear in the  “component” menu, send an email to boost-owner@lists.boost.org requesting that it be added.  If you can't find an obviously-correct owner, try to put the maintainer's email address in the Ticket's Cc: list.  Probably someone needs to start a Wiki page that identifies Boost library maintainers by their Trac/SVN ids.
    26 
    27 === Close Invalid “Feature Requests” ===
    28 
    29 “Feature requests” that are actually suggestions for new Boost libraries are invalid—as tickets, that is.  There's nobody to whom they can be assigned. The reporter should be directed to start a discussion in some forum where a qualified domain expert is likely to be listening, or to [http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?WantedLibraries this page] on the [http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl Boost users' wiki], …or you can enter the suggestion there yourself.
     16 * '''Triage Unassigned Tickets'''. report:10 shows all tickets that haven't been assigned to real developers.
     17  * '''Assign Component and Owner''': Set the ticket's “component” field to the right library and assign the ticket to the maintainer of that library.
     18   * If the right library doesn't appear in the  “component” menu, send an email to boost-owner@lists.boost.org requesting that it be added.
     19   * If you can't find an obviously-correct owner, try to put the maintainer's email address in the Ticket's Cc: list.  [[br]] (Probably someone needs to start a Wiki page that identifies Boost library maintainers by their Trac/SVN ids.)
     20  * '''Close Invalid “Feature Requests”''': “Feature requests” that are actually suggestions for new Boost libraries are invalid—as tickets, that is.  There's nobody to whom they can be assigned. The reporter should be directed to start a discussion in some forum where a qualified domain expert is likely to be listening, or to [http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?WantedLibraries this page] on the [http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl Boost users' wiki], …or you can enter the suggestion there yourself.