[samigo-team] test fest for next meeting (4/3)

[Jim Mezzanotte]

I'm up for doing another test fest for the next meeting (4/3). It
might also help us establish a baseline for how much QA will be needed
for release.

Best,
Jim Mezzanotte
rSmart

On Thu, Mar 22, 2012 at 3:00 PM,
<samigo-team-request at collab.sakaiproject.org> wrote:
> Send samigo-team mailing list submissions to
>        samigo-team at collab.sakaiproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://collab.sakaiproject.org/mailman/listinfo/samigo-team
> or, via email, send a message with subject or body 'help' to
>        samigo-team-request at collab.sakaiproject.org
>
> You can reach the person managing the list at
>        samigo-team-owner at collab.sakaiproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of samigo-team digest..."
>
>
> Today's Topics:
>
>   1. Update on status of SAMigo 2.9 release (Jacqueline Mai Krueger)
>   2. Re: Update on status of SAMigo 2.9 release (Ward, Lynn E.)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 21 Mar 2012 16:27:09 -0700
> From: Jacqueline Mai Krueger <jamai at stanford.edu>
> Subject: [samigo-team] Update on status of SAMigo 2.9 release
> To: "samigo-team at collab.sakaiproject.org"
>        <samigo-team at collab.sakaiproject.org>
> Message-ID: <4F6A63CD.7020202 at stanford.edu>
> Content-Type: text/plain; charset="iso-8859-1"
>
> During Tuesday's meeting, we mentioned that there were a couple of code
> contributions that were problematic. For those interested in the
> specific JIRA numbers, they are
> https://jira.sakaiproject.org/browse/SAM-1472
> https://jira.sakaiproject.org/browse/SAM-1438
> These issues are not critical and are not blocking the SAMigo 2.9
> release. If there's a need to cut a 2.9 tag soon, then we can revert to
> a version that does not contain the contributed code. We also found out
> that we will have help from the CLE release team so release-related
> concerns are a non-issue.
>
> An action item for Stanford from Tuesday's meeting was to find out how
> much QA work is left. Per my record, the last SAMigo test fest was
> conducted on 11.29.11. The SAMigo code has changed since then so we
> would need to cut a new SAMigo 2.9 tag and conduct testing against this
> new tag.
>
> *What kind of help do we need?*
> Lots of QA!
> Stanford will cut a 2.9 tag but need one of the 2.9 QA servers to update
> to this latest tag (I'll send a follow-up once I know specifics)
> *
> *If we don't have agenda items for the next meeting 04.03, perhaps we
> could devote time to another test fest. Would anyone be up to this?
>
> Thanks,
> Jackie
> --
> Jacqueline Mai Krueger
> User Experience Specialist
> Academic Computing Services - CourseWork
> Stanford University
> <http://www.getpostbox.com>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/samigo-team/attachments/20120321/998ec037/attachment-0001.html
>
> ------------------------------
>
> Message: 2
> Date: Wed, 21 Mar 2012 23:47:41 +0000
> From: "Ward, Lynn E." <leward at iupui.edu>
> Subject: Re: [samigo-team] Update on status of SAMigo 2.9 release
> To: Jacqueline Mai Krueger <jamai at stanford.edu>
> Cc: Samigo Team <samigo-team at collab.sakaiproject.org>
> Message-ID: <1DF948DE-DDC7-442E-926B-94EF9DCA66A6 at iupui.edu>
> Content-Type: text/plain; charset="us-ascii"
>
> SAM-1472 is a big problem for large sites with groups. Perhaps it should be escalated to critical?  As Ying mentioned in the Jira, she developed a fix that dowsn't involve kernel change and makes a big performance improvement. Not sure what it would take to merge it, as we've got a lot of customizations.
>
> Yes, I'm definitely up for another test test. :-)
>
> Sent from my iPad
>
> On Mar 21, 2012, at 7:27 PM, "Jacqueline Mai Krueger" <jamai at stanford.edu<mailto:jamai at stanford.edu>> wrote:
>
> During Tuesday's meeting, we mentioned that there were a couple of code contributions that were problematic. For those interested in the specific JIRA numbers, they are
> https://jira.sakaiproject.org/browse/SAM-1472
> https://jira.sakaiproject.org/browse/SAM-1438
> These issues are not critical and are not blocking the SAMigo 2.9 release. If there's a need to cut a 2.9 tag soon, then we can revert to a version that does not contain the contributed code. We also found out that we will have help from the CLE release team so release-related concerns are a non-issue.
>
> An action item for Stanford from Tuesday's meeting was to find out how much QA work is left. Per my record, the last SAMigo test fest was conducted on 11.29.11. The SAMigo code has changed since then so we would need to cut a new SAMigo 2.9 tag and conduct testing against this new tag.
>
> What kind of help do we need?
> Lots of QA!
> Stanford will cut a 2.9 tag but need one of the 2.9 QA servers to update to this latest tag (I'll send a follow-up once I know specifics)
>
> If we don't have agenda items for the next meeting 04.03, perhaps we could devote time to another test fest. Would anyone be up to this?
>
> Thanks,
> Jackie
> --
> Jacqueline Mai Krueger
> User Experience Specialist
> Academic Computing Services - CourseWork
> Stanford University
> <http://www.getpostbox.com>
> _______________________________________________
> samigo-team mailing list
> samigo-team at collab.sakaiproject.org<mailto:samigo-team at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/samigo-team
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/samigo-team/attachments/20120321/b1819685/attachment-0001.html
>
> ------------------------------
>
> _______________________________________________
> samigo-team mailing list
> samigo-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/samigo-team
>
>
> End of samigo-team Digest, Vol 9, Issue 10
> ******************************************