[WG: Sakai QA] [sakai2-tcc] Status of 2.9.1 RC01 as of Friday, 30 Nov

Matthew Jones matthew at longsight.com
Fri Nov 30 10:21:47 PST 2012


Yea, generally what you're describing is what happens. Trunk right now is
what will eventually need to be copied to represent the next version of
Sakai. At that point only bug fixes and approved feature changes are
supposed to be merged. Trunk prior to that was copied on Dec 15th 2011 to
2.9.x as 2.9.0-a01.

2.10.x (Tentatively) probably won't be created until January 2013, so there
will be a year of changes, some of which were merged into 2.9.x, some that
weren't. There really isn't any way to know in jira which issues are unless
someone wrote a script that scanned the svn logs from when 2.9.x and 2.10.x
was cut, looked at the comments in JIRA (like MSGCNTR-### SAK-##, KNL-##)
and updated the fix version in Jira directly and correctly.

This is a possibility but might take at least a day to write this I'd guess
and have it all work without any issues. So sounds like a good project if
you wanted to work on it! :)


On Fri, Nov 30, 2012 at 11:27 AM, Neal Caidin <
nealcaidin at sakaifoundation.org> wrote:

> How much QA would be needed after rolling back ? It looks like there are
> code changes to Gradebook, Assignments, and Samigo Tests and Quizzes?  Just
> wondering if there are any risks to rolling this back. If little or no
> risk, and if not too much QA is involved, then that sounds to me like an
> option worth considering (unless it gets fixed).
>
> Separate issue (Jira-ish) - for future cases where we take everything in
> trunk and roll it into an alpha release (which I think is how 2.9.0-a01 was
> created?) , could we have some kind of tag or bulk comment to explicitly
> indicates this? Otherwise, the only way to really know this is in 2.9.0 is
> to rely on the fixVersion and to look at the commit dates, and be aware of
> when the creation happened (or something like that)? Seems confusing to me
> :-p
>
> Thanks
>
> Neal
>
>
>
>
> On Fri, Nov 30, 2012 at 10:39 AM, Bryan Holladay <holladay at longsight.com>wrote:
>
>> Is anyone planning on working on this?  If not, then we should remove
>> this feature for 2.9.1 and put it back in once it's fixed.
>>
>> -Bryan
>>
>>
>> On Fri, Nov 30, 2012 at 10:31 AM, Matthew Jones <matthew at longsight.com>wrote:
>>
>>> With both of these *easier* fixes in (#1 being the easiest) the
>>> gradebook would still be slow if the site did have groups and the linked
>>> assignments actually were grouped.
>>>
>>> 1) Fixes the case where the course has no groups at all
>>> 2) Fixes the case where the course has groups but the linked assignments
>>> aren't grouped
>>> 3) (Which is more complex and ideas suggested as comments on the ticket
>>> by Noah) Fixes the case where the course has groups and the linked
>>> assignments are grouped.
>>>
>>> This seems in testing to be more of a problem (slower) with linking to
>>> Samigo rather than Assignments, but I'm not sure about Lessons (which also
>>> links, but unsure if it supports grouping)
>>>
>>> The check in testing is about 0.5 - 1 second extra load time for every
>>> assignment linked to gradebook, so it can get pretty significant, it also
>>> was filling the log with dozens of error messages.
>>>
>>> 2012-11-29 14:14:34,863 ERROR http-bio-42048-exec-28
>>> org.sakaiproject.tool.assessment.services.assessment.PublishedAssessmentService
>>> - java.lang.NumberFormatException: For input string:
>>> "/assignment/a/2012fa-cis-110-190/2630d6ac-2c9a-4bcf-803f-b615b153667c"
>>>
>>>
>>> On Fri, Nov 30, 2012 at 10:00 AM, Bryan Holladay <holladay at longsight.com
>>> > wrote:
>>>
>>>> If we could put a band-aide on SAK-22978<https://jira.sakaiproject.org/browse/SAK-22978> at
>>>> a minimum, I would be ok with a 2.9.1 release and have a complete fix for
>>>> 2.9.2.  A simple band-aide would be two parts:
>>>>
>>>> 1) Check if a site has groups before looking up group member items
>>>> 2) Add a cache in the gradebook service to store the results so it only
>>>> has to take 15 seconds to load for 1 unlucky user every once in a while
>>>>
>>>> Without this minimal fix, my vote is -1
>>>>
>>>> -Bryan
>>>>
>>>>
>>>> On Fri, Nov 30, 2012 at 9:49 AM, Neal Caidin <
>>>> nealcaidin at sakaifoundation.org> wrote:
>>>>
>>>>> [sent to QA, Dev, CLE Release, and TCC lists]
>>>>>
>>>>> Hi All,
>>>>>
>>>>> We are iffy (uncertain) at this point for the first Release Candidate
>>>>> for 2.9.1,  2.9.1-rc01,  for next Friday, Dec 7, but still possible.
>>>>>
>>>>> The two main issues are whether we will get the updated Help
>>>>> documentation integrated (SAK-22891). The other is a potential blocker for
>>>>> performance in the Gradebook -
>>>>> https://jira.sakaiproject.org/browse/SAK-22978 - "Performance issue
>>>>> with group member items in gradebook (SAK-19668)", which came out of the
>>>>> new 2.9 feature https://jira.sakaiproject.org/browse/SAK-19668 -
>>>>> "Gradebook - Student Grade Report - items assigned to groups in Tests &
>>>>> Quizzes, Assignments, and Forums should only appear to group members". One
>>>>> or both of these issues (SAK-22891 and SAK-22978) could cause delays.
>>>>> Ideally, we would get both fixed. If SAK-22978 does not get fixed in time,
>>>>> we might want to consider whether to proceed with 2.9.1 anyway and fix this
>>>>> problem for 2.9.2. Just a thought. For now, let's wait and see what happens.
>>>>>
>>>>> Otherwise, we have a lot of nice fixes for 2.9.1 .  I've made two
>>>>> temporary filters in Jira:
>>>>>
>>>>> "2.9.1 Triage" - lists all the issues that are currently tagged for
>>>>> 2.9.1 (not all may make it). -
>>>>> https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=13619
>>>>> "2.9.1 Triage Review" - lists issues which may need additional review
>>>>> (development, testing, etc) to get into 2.9.1 -
>>>>> https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=13620
>>>>>
>>>>> At this moment we have 52 issues with the "291triage" tag, out of
>>>>> which 35 have been fixed and verified, with some already having been
>>>>> merged.
>>>>>
>>>>> The basic QA strategy will be to retest the issues that are merged
>>>>> into 2.9.1-RC01 and look for regressions around those merges.
>>>>>
>>>>> Thanks for your attention.
>>>>>
>>>>> Regards,
>>>>>
>>>>>  Neal Caidin
>>>>>
>>>>> Sakai CLE Community Coordinator
>>>>> nealcaidin at sakaifoundation.org
>>>>> Skype: nealkdin
>>>>> AIM: ncaidin at aol.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> sakai2-tcc mailing list
>>>>> sakai2-tcc at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> sakai2-tcc mailing list
>>>> sakai2-tcc at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>>>
>>>>
>>>
>>
>
>
> --
> Neal Caidin
> Sakai CLE Community Coordinator
> nealcaidin at sakaifoundation.org
> skype: nealkdin
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20121130/acfe5a26/attachment.html 


More information about the sakai-qa mailing list