[sakai2-tcc] Cross cutting concerns and prompt patching during a major release

[May, Megan Marie]

I'm not sure I see the distinction between a dropdown with three states (btw, what do they mean?) and a checkbox.   If someone has gone to the work to attach a patch (for trunk or a branch), it seems like it is the responsibility of the project leads to be responsive to that.   What seems important is that the lead *knows* there is something that requires their action.

Am I missing something? 

-----Original Message-----
From: sakai2-tcc-bounces at collab.sakaiproject.org [mailto:sakai2-tcc-bounces at collab.sakaiproject.org] On Behalf Of csev
Sent: Thursday, November 25, 2010 11:25 AM
To: sakai2-tcc at collab.sakaiproject.org Committee
Cc: Alan Berg
Subject: Re: [sakai2-tcc] Cross cutting concerns and prompt patching during a major release


On Nov 25, 2010, at 10:44 AM, Anthony Whyte wrote:

> One relatively painless process tweek we could implement is to add a "Patch attached" checkbox to our tickets in Jira.  This would add a fourth checkbox to the Jira form but it would help simplify tracking the progress of tickets that include a submitted patch.  I am not suggesting this a solution to the problem of patch management but as a tweek that may help us better measure the extent of the problem.

I don't think a checkbox of "patch attached" is all that valuable.  I prefer my proposal that says "This JIRA is trunk-ready" - it communicates far more useful information to a project lead.  Just having a patch attached is zero indication that this is something that needs a little bit of immediate attention.

/Chuck

_______________________________________________
sakai2-tcc mailing list
sakai2-tcc at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc