Differences between revisions 2 and 11 (spanning 9 versions)
Revision 2 as of 2012-03-17 19:23:21
Size: 681
Editor: roed
Comment:
Revision 11 as of 2012-03-19 04:56:54
Size: 1136
Editor: roed
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
=== Line Comments === Line Comments ===
Line 6: Line 6:

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

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

[[/SystemRequirements Requirements and desired features]] of a new workflow.
Line 11: Line 17:
=== Bandaids === === Stopgaps (formerly, "bandaids") ===
Line 13: Line 19:
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.  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.
  * 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

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:

/SystemRequirements Requirements and desired features of a new workflow.

Require reviewer

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

Stopgaps (formerly, "bandaids")

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

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)