Changes between Version 5 and Version 6 of DebugProtocol

Timestamp:

06/06/11 17:01:40 (14 years ago)

Author:

Brandon Shroyer

Comment:

—

DebugProtocol

@@ -7 +7 @@
  *   That their environment settings, compiler flags, and submission scripts are correct.
  *  They are using the most current version of the code.
+
+3.  ''Prioritization:''  The ticket owner will report back to the debug team leader, who will decide whether or not to change the ticket's priority.  Most tickets will probably fall within the 2-4 range; only the debug team leader may set tickets as priority 1.
 
 3.  ''Reproduction:''  The ticket owner should work with the reporter to reproduce the bug.  This will involve access to some or all of the following:
@@ -24 +26 @@
     * Set {{{InterpOpts}}} to 0 in {{{physics.data}}}.
     * Use a different problem module.
-  * Once the problem goes away, then try switching back on things that had been turned off until you have the closest thing to the original setup that still works.  
+
+  Once the problem goes away, then try switching back on things that had been turned off until you have the closest thing to the original setup that still works.  
  * Prepare a report (summary comment on the ticket) for weekly debug meetings describing the results with possible courses of action.