|
Size: 1002
Comment:
|
Size: 1138
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| [[/SystemRequirements | Requirements and desired features]] of a new workflow. | |
| Line 16: | Line 17: |
| === Bandaids === | === Stopgaps (formerly, "bandaids") === |
| Line 19: | Line 20: |
| * 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 |
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:
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.
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
Patchbot
Fix patchbot so that it doesn't timeout on unbroken code.
Doctesting
Finish the new doctesting code: #12415
