[cle-release-team] [Building Sakai] [WG: Sakai QA] Sakai CLE 2.9.0 release status

[Aaron Zeckoski]

I would encourage you ro think of a process that uses jira itself as a
way to know if an issue is being tested. This may be an adjustment in
the JIRA workflow but I can make that without too much trouble. The
problem with the google docs thing is that it doesn't scale up very
well and it requires insider knowledge so it is a barrier to community
participation.

Also, in the current workflow, there is a "Verified" status which is
what issues should be set to when testing is complete. So anything not
verified yet will be marked as "resolved - fixed" and once testing is
complete it is marked as "verified".

-AZ


On Mon, Mar 26, 2012 at 6:58 AM, Diego del Blanco Orobitg
<diego.delblanco at samoo.es> wrote:
> Dear Rob:
>
> We are going to begin to test the jira issues as Aaron said. To coordinate with you and don't duplicate work, we can create a shared document (in google docs or in a confluence page...), where each time one of us selects a jira to test, we need to add it to the document, so it's easy to check if an issue is "in use" at that moment. There is only need to search in the document. If it's not, then it's free.
>
> And in that way we have the full list of jiras tested by each one too.
>
> Aaron do you think this is good way or do you recommend other way as can be to put comments directly on Jira's indicating that we are working on this issue?
>
> I think in the shared document will be quicker to search "free issues" to work with.
>
> Other question... Once tested a Jira if everything is ok.. do we need to modify something in the Jira (add a comment or change state) or only communicate it to the team?
>
> Thanks
>
> Diego.
>
>
> -----Mensaje original-----
> De: azeckoski at gmail.com [mailto:azeckoski at gmail.com] En nombre de Aaron Zeckoski
> Enviado el: viernes, 23 de marzo de 2012 22:36
> Para: Miguel Carro Pellicer; Rob.Egan at marist.edu; Diego del Blanco Orobitg
> CC: Sam Ottenhoff; cle-release-team at collab.sakaiproject.org
> Asunto: Re: [Building Sakai] [WG: Sakai QA] Sakai CLE 2.9.0 release status
>
> Samoo guys,
> Here is the filter of items to QA in order for 2.9. There are quite a few (over 600) and there will be more coming in the following weeks.
> Just start cranking through them and you can give a status update at the meeting next week.
>
> https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=13243
>
> I am copying in Rob from Marist since he does some QA as well and you guys might want to coordinate some.
>
> -AZ
>
>
>> El 22/03/2012 14:07, Aaron Zeckoski escribió:
>>
>> Yes, they are always at 10am US NY time on thursdays.
>> I will double check with the group and send you something later today (maybe a JIRA filter with a series of tickets in it).
>> -AZ
>>
>> On Thu, Mar 22, 2012 at 9:03 AM, Miguel Carro Pellicer <miguel.carro at samoo.es> wrote:
>>
>> Got it, i think we can help in those activities.
>>
>> Assign me some Jiras and we will verify/validate each ticket in the affected QA servers. Additionaly, we can propose a solution if the Jira requires a developer intervention.
>>
>> Usually the meetings are at the same hour? We're in GMT+1
>>
>> Regards, Miguel.
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> -----
> No se encontraron virus en este mensaje.
> Comprobado por AVG - www.avg.com
> Versión: 2012.0.1913 / Base de datos de virus: 2114/4893 - Fecha de publicación: 03/25/12
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team



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