Jason Grout wrote: > > A suggestion for a workflow based on the Drupal ticket system is here: > > http://groups.google.com/group/sage-devel/browse_thread/thread/d794dcc6f98c17fe/356342ea14f6d265?q=drupal+group:sage-devel#356342ea14f6d265
To elaborate, here are some stages that our patches seem to go through: * active * active (needs more info) * patch (needs work) * patch (needs documentation/testing work) -- this is for doctest fixing, adding doctests, or documentation that needs to be fixed (e.g., improper rest structure) * patch (needs review) * patch (positive review) * fixed * duplicate * invalid * bydesign In split out code work and documentation work, since it seems that documentation work often can be done by someone who may or may not understand the code deeply. And here are instructions for modifying trac.ini to implement something like this: http://trac.edgewall.org/wiki/TracWorkflow Jason -- Jason Grout --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
