On Oct 1, 2009, at 2:43 PM, Jason Grout wrote:

> In order to help organize the flow of work on trac, here is a proposed
> workflow for trac tickets (see attached image or
> http://sage.math.washington.edu/home/jason/sage_workflow.png).  The  
> "*"
> state is a wildcard for any state (so, for example, you can go from  
> any
> state to "needs_work", "needs_review", or "closed").
>
> What do people think?  In this workflow, I tried to make it
> patch-centric, in that there is no "assigned" state.  Owners on a  
> ticket
> can be assigned/accepted as they will, but the status of the ticket
> reflects the state of the work on the ticket, not who owns it.

I think process rather than ownership centric is a good move.  
Certainly better than what we have. Is there a "merged" transition  
from positive review to closed?

> I also separated the "needs work" into two categories, because it  
> seems
> that often there are people that are comfortable working on
> documentation and testing issues that aren't comfortable working on  
> the
> code.  This allows someone in that category to easily find work  
> they can do.
>
> I also separated out the "needs info" state into a state that is  
> for new
> tickets (e.g., bug reports where we still need the make of the
> computer), and needs info on other tickets where work has already been
> started (e.g., there is a design discussion on sage-devel about how to
> proceed).  Comments on this separation?
>
> Also, I was thinking about adding a third work category, needs_rebase.
> Thoughts?  Or should rebase work just be part of needs_work and
> needs_doc_work?

How about "incomplete" or "undecided" for needs_info? (Maybe  
needs_info is the best name, just throwing ideas out there.)

I think rather than having several kinds of needs_work states, we  
should have a new field. Thus we could have "needs_work" with the  
"issues" field being documentation, doctests, rebasing, ...

- Robert


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to