We just finished putting the new workflow on trac.  From now on, instead 
of declaring the status of a ticket using "[with patch, needs review]" 
and other such annotations on the title, please select the appropriate 
status at the bottom of the ticket.  For a typical ticket, you'll be 
able to choose between:

needs info -- this is for tickets that are currently undergoing 
discussion or are undergoing work outside of the sage community (for 
example, in an upstream project).  The information is needed to move the 
ticket forward---these tickets are, in a sense, on hold.

needs work -- this is for tickets on which some work has been done, but 
more work is needed.  Usually, this means that a patch or spkg is on the 
ticket, but it is not yet ready for review.  This is also the status for 
tickets that need some more work after a review.  The "Work issues" 
field should be used to indicate the general areas of work.  I propose 
that we use standardized strings like "docs" and "code" in the "Work 
issues" box.  More specific instructions can go into a comment.

needs review -- this is for tickets that are awaiting review.

positive review -- this is for tickets having a positive review


The assigning of tickets has now been separated from the ticket 
workflow.  Feel free to the ticket owner information to organize work.


One note: Currently the "Work issues" field is a text box, and so 
suffers the same problems we had with title annotations (e.g., 
misspellings omit the ticket from a report, etc.).  I figured we'd use 
the textbox until we had a set of conventions for general areas of work, 
and then we'd make the most common areas into checkboxes.

A second note: in the previous workflows, there were two "needs info" 
states.  I've combined these into one 'needs info' state, since there 
weren't that many tickets in it and it didn't seem to justify the 
separation.

A third note: can we stop automatically setting owners on new tickets?

I've changed all of the reports to pull their information from the new 
states, and deleted a few reports were obsolete.

Please reply with any comments.

Thanks,

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

Reply via email to