Differences between revisions 1 and 5 (spanning 4 versions)
⇤ ← Revision 1 as of 2012-03-17 19:19:11 →
Size: 543
Editor: roed
Comment:
← Revision 5 as of 2012-03-18 16:17:57 → ⇥
Size: 981
Editor: jen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
   * 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)
  * Implement a system requiring authors of tickets to suggest a reviewer (while providing defaults)
   * Come up with a way to ensure that critical tickets [[http://trac.sagemath.org/sage_trac/ticket/11358|like this]] don't get lost beneath the radar.
   * Fix patchbot
   * Finish the new doctesting code: [[http://trac.sagemath.org/sage_trac/ticket/12415|#12415]]		 === Line Comments ===

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)

Sample ticket illustrating some nitty gritty details involved in using git:

 * http://trac.sagemath.org/sage_trac/ticket/12685


=== Require reviewer ===

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

=== Bandaids ===

Come up with a way to ensure that critical tickets [[http://trac.sagemath.org/sage_trac/ticket/11358|like this]] don't get lost beneath the radar.
Idea: checkbox 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.

=== Patchbot ===

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

=== Doctesting ===

Finish the new doctesting code: [[http://trac.sagemath.org/sage_trac/ticket/12415|#12415]]

Projects

Line Comments

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)

Sample ticket illustrating some nitty gritty details involved in using git:

Require reviewer

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

Bandaids

Come up with a way to ensure that critical tickets like this don't get lost beneath the radar. Idea: checkbox 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.

Patchbot

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

Doctesting

Finish the new doctesting code: #12415

review2/Projects (last edited 2012-03-23 06:40:28 by roed)