[WG: Sakai QA] [cle-release-team] Question about Jira workflow

Wed Sep 5 05:56:05 PDT 2012

Taggable isn't in contrib anymore..it's been in core sakai for quite a
while.  Feel free to just migrate that whole project over to SAK if you
want.

Chris

On 9/5/12 8:48 AM, "Aaron Zeckoski" <azeckoski at unicon.net> wrote:

>OK, I migrated the following projects.
>PRFL
>SHORTURL
>BLTI
>SRCH
>RES
>
>It took jira a chunk of time to complete but everything seems to have
>migrated correctly.
>
>The following projects are still on the old "Sakai" scheme (which is
>basically the same as the JIRA default with just a name change):
>Contrib: Big Blue Button
>Contrib: Delegated Access
>Contrib: Markup
>Contrib: Taggable
>Contrib: XWiki
>Hybrid
>
>I think those should be switched over to at least the default JIRA
>schema (or maybe to the new workflow)? probably but it is really up to
>the project leads on those ones. The other projects not using the new
>workflow are just using the JIRA default workflow.
>
>Here are the listed projects and leads (from the CLE projects not
>using the new scheme):
>MSND - carl at hallwaytech.com
>LSNBLDR - hedrick at rutgers.edu
>MSGCNTR - sakai-msgcntr-team at collab.sakaiproject.org
>
>I'm not sure we can just switch them over because the default workflow
>is a bit different from the new workflow (it leaves out the Needs
>Review and the QA portions of the workflow).
>-AZ
>
>
>On Tue, Sep 4, 2012 at 8:35 PM, Steve Swinsburg
><steve.swinsburg at gmail.com> wrote:
>> They should all be switched.
>>
>> I have two of them, PRFL & SHORTURL. Switch them :)
>> Chuck has BLTI but I'm sure would be happy to go with the flow since
>>others in this group also work on it.
>> SRCH and RES, also controlled by this group (mainly Horwitz but there
>>are others)
>>
>> For the others, MSND, LSNBLDR and MSGCNTR, contact the leads though I
>>haven't seen any special workflow in any of them so its more likely that
>>they just haven't been switched to the new one, rather than they are
>>relying on a special workflow (which happened to be the old default ;)
>>
>> cheers,
>> S
>>
>>
>> On 05/09/2012, at 12:49 AM, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>>
>>> Unless they agree to use the workflow, then I guess you would need to
>>> do whatever process they have decided on for that project. I don't
>>> know what that process would be but I expect it would vary from
>>> project to project.
>>> I do think that if a project wants to not use the main Sakai workflow
>>> that they should probably be required to provide some documentation on
>>> how their workflow and QA process work.
>>> -AZ
>>>
>>>
>>> On Tue, Sep 4, 2012 at 10:45 AM, Neal Caidin
>>> <nealcaidin at sakaifoundation.org> wrote:
>>>> Okay. I guess for the non-core projects, we would just put our QA
>>>>status in the comments, or Reopen the ticket if it fails.  Does that
>>>>sound about right?
>>>>
>>>> Thanks,
>>>> Neal
>>>>
>>>>
>>>> On Sep 4, 2012, at 10:21 AM, Aaron Zeckoski <azeckoski at unicon.net>
>>>>wrote:
>>>>
>>>>> I don't think they are, but we can copy in the QA list on this reply:
>>>>>
>>>>> Neal,
>>>>> I switched over the core projects and ones controlled by the CLE team
>>>>> (or me) to use the new workflow. Other projects are welcome to use it
>>>>> as well but I did not force it on any of them.
>>>>>
>>>>> I think the new workflow is better personally but I think it is up to
>>>>> the individual project teams to make that decision. I suggest you
>>>>> touch base with them and find out which ones are willing to switch
>>>>> over.
>>>>> :-)
>>>>> -AZ
>>>>>
>>>>>
>>>>> On Tue, Sep 4, 2012 at 10:18 AM, Neal Caidin
>>>>> <nealcaidin at sakaifoundation.org> wrote:
>>>>>> I just realized that I'm making an assumption that everyone on the
>>>>>>CLE
>>>>>> Release team is in the Jira QA group? Otherwise, I don't think you
>>>>>>would see
>>>>>> the difference between the workflows.
>>>>>>
>>>>>> Thanks,
>>>>>> Neal
>>>>>>
>>>>>> On Sep 4, 2012, at 10:01 AM, Neal Caidin
>>>>>><nealcaidin at sakaifoundation.org>
>>>>>> wrote:
>>>>>>
>>>>>> Hi CLE Release team,
>>>>>>
>>>>>> I was going through the Blocker/Critical tickets which need QA -
>>>>>> 
>>>>>>https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&re
>>>>>>questId=13399
>>>>>>
>>>>>> and I noticed that some of the tickets have the option for
>>>>>>indicating the
>>>>>> issue was Tested, Close with Testing or Start QA (what I would
>>>>>>expect).
>>>>>> Other issues only had the option to Close or Reopen the issue. RES
>>>>>>issues
>>>>>> had the option to Close, Tested, or Re-Open.
>>>>>>
>>>>>> My hypothesis is that the QA workflow is not the same for all
>>>>>>projects?  I
>>>>>> looked at
>>>>>> 
>>>>>>https://confluence.sakaiproject.org/display/MGT/Sakai+Jira+Guidelines
>>>>>> , but
>>>>>> nothing like that is mentioned.
>>>>>>
>>>>>> Based on looking at samples of tickets, it seems to me that SAK,
>>>>>>KNL, SAM,
>>>>>> STAT, and POLL use the same workflow (expected workflow) but that
>>>>>>MSGCNTR,
>>>>>> MSND, LSNBLDR, SHORTULR, SRCH, BLTI, and PRFL use a different
>>>>>>workflow. And
>>>>>> RES may be using it's own. A couple of example tickets below. KNL
>>>>>>behaves as
>>>>>> I expect, but not MSGCNTR.
>>>>>>
>>>>>>
>>>>>> MSGCNTR-683
>>>>>>
>>>>>>
>>>>>> KNL-955
>>>>>>
>>>>>> This is important because at a minimum I need to make sure the QA
>>>>>>process
>>>>>> and documentation are reflecting reality, and also because we might
>>>>>>want to
>>>>>> consider rationalizing the processes at some point in the future.
>>>>>>
>>>>>> Is my hypothesis correct? If not, why am I seeing the discrepancy in
>>>>>> behavior?
>>>>>>
>>>>>> This came up because I was working with a new QA tester this
>>>>>>morning to get
>>>>>> him started and the first issue he picked to work on was for PRFL
>>>>>>and it
>>>>>> doesn't have a Start QA button.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Neal Caidin
>>>>>>
>>>>>> Sakai CLE Community Coordinator
>>>>>> nealcaidin at sakaifoundation.org
>>>>>> Skype: nealkdin
>>>>>> AIM: ncaidin at aol.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>> _______________________________________________
>>>> 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
>>> _______________________________________________
>>> cle-release-team mailing list
>>> cle-release-team at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>
>> _______________________________________________
>> 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
>_______________________________________________
>cle-release-team mailing list
>cle-release-team at collab.sakaiproject.org
>http://collab.sakaiproject.org/mailman/listinfo/cle-release-team