Diff for "review2/Projects"

Differences between revisions 7 and 14 (spanning 7 versions)

Projects

Set up a system that allows line by line comments (like Google's internal Mondrian system, or the open source versions Rietveld or Review Board)

Proposals for new workflows.

Implement a system requiring authors of tickets to suggest a reviewer (while providing defaults)

Come up with a way to ensure that critical tickets like this don't get lost beneath the radar.

Fix patchbot so that it doesn't timeout on unbroken code.

Finish the new doctesting code: #12415

Make a trac wiki page that's linked to by the "View Tickets" button that organizes the reports in a more useful way.

-  ⇤ ← Revision 7 as of 2012-03-18 22:45:17 → 
  Size: 1002
  Editor: jen
  Comment:
+   ← Revision 14 as of 2012-03-19 19:13:28 → ⇥
  Size: 1205
  Editor: roed
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 7:
-Sample ticket illustrating some nitty gritty details involved in using git:
+[[/SystemRequirements | Requirements and desired features]] of a new workflow.
 Line 9:
-  * http://trac.sagemath.org/sage_trac/ticket/12685
+[[/SystemProposals | Proposals]] for new workflows.
-Line 16:
+Line 15:
-=== Bandaids ===
+=== Stopgaps (formerly, "bandaids") ===
-Line 19:
+Line 18:
-  * Idea: adding another keyword on tickets + warning
  * If we're going to go through the ~3000 active tickets to mark these, we should figure out if we want to do anything else.
+  * Here's what we're doing: http://trac.sagemath.org/sage_trac/ticket/12691
  * For an example, see http://trac.sagemath.org/sage_trac/ticket/12509 and its stopgap http://trac.sagemath.org/sage_trac/ticket/12692
-Line 29:
+Line 28:
+=== Better Reports ===

Make a trac wiki page that's linked to by the "View Tickets" button that organizes the reports in a more useful way.