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

[Aaron Zeckoski]

There is always the contributed patch case type. Making a contributed
patch case and linking it to the original would certainly flag things
up (though it is a bit of a pain to have multiple tickets so I don't
really love this as an option).
-AZ


On Thu, Nov 25, 2010 at 10:24 AM, csev <csev at umich.edu> wrote:
>
> 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
>



-- 
Aaron Zeckoski - Software Engineer - http://tinyurl.com/azprofile