[Building Sakai] URGENT - Samigo: statistics do not show when random draw from pool is used
David Horwitz
david.horwitz at uct.ac.za
Wed Mar 14 13:34:31 PDT 2012
The UCT 2.8 msub branch includes this fix and some of the performance
optimisations that haven't been merged back. People are welcome to use
this as a post-2.8.3 if they want (this is what Wits is doing)
D
On 03/14/2012 08:47 PM, Karen Tsao wrote:
> After discussing within the Samigo team, we agree with Sam and Matthew
> that this is more like a new feature instead of a bug. So we would
> like to be more conservative and decide not to merge to 2.8.x.
>
> For schools want to have this feature, please follow Sam's
> instruction above to merge code from trunk.
>
> Thanks,
> Karen
>
>
> On Mon, Mar 12, 2012 at 3:41 PM, Matthew Jones <matthew at longsight.com
> <mailto:matthew at longsight.com>> wrote:
>
> I agree, msub is the place for this in a 2.8 world. This is what
> it looks like UCT did for it today on revision (105667)
> https://source.sakaiproject.org/svn//msub/uct.ac.za/samigo-2.8.3/
>
> That way it at least has some confirmation that it is tested and
> running in production somewhere. Any change of this
> size definitely has the possibility of causing regressions or edge
> cases and rarely gets the QA it needs. There are also related
> issues, some of them open, I can't tell if they are regressions or
> not without further investigation.
>
> People depend on these .x branches for blocker/critical bug fixes
> and this looks like a minor feature request had been requested 6
> years ago and was fixed 2 years ago.
>
> However Samigo is a rare project in the CLE that has it's own team
> and can release how they want, but I would still advise that this
> be kept in a separate institutional branch or a some type of
> separate feature-backport branch.
>
> -Matthew
>
>
> On Mon, Mar 12, 2012 at 6:12 PM, Sam Ottenhoff
> <ottenhoff at longsight.com <mailto:ottenhoff at longsight.com>> wrote:
>
> SAM-1620 could be interpreted as a new feature, and the Sakai
> community has agreed not to introduce large, new features into
> maintenance branches. The idea of the maintenance branch is
> to create a stable environment for bug fixes only.
>
> Institutions that want to introduce new features into their
> environment need to learn how to use the "svn merge" command
> to bring a feature from trunk into their local code.
>
> The basic process of merging a fix from trunk to a branch:
>
> $ cd your-local-samigo
> $ svn merge -c ######
> https://source.sakaiproject.org/svn/sam/trunk/
>
> To figure out what the "#####", you need to go into JIRA and
> investigate the "Subversion Commits" tab. SAM-1620 is
> extremely complex so you will need to ignore all of the many
> branch commits and look for the final commit made to trunk.
>
> --Sam
>
>
> On Mon, Mar 12, 2012 at 6:01 PM, David Wafula
> <davidwaf at gmail.com <mailto:davidwaf at gmail.com>> wrote:
>
> Thanks Karen,
> That explains why nothing was changing. Now, correct me if
> am wrong
> please. SAM-1620 seems to suggest this was never fixed in
> 2.8.x ,
> right?
> As it stands, to fix this, I have to get the diff against
> trunk and
> apply it to 2.8.3 ? So will appreciate the patch for
> 2.8.x..especially .3
>
> thanks.
>
> On Mon, Mar 12, 2012 at 7:33 PM, Karen Tsao
> <ktsao at stanford.edu <mailto:ktsao at stanford.edu>> wrote:
> > Hi David,
> >
> > SAM-1552 is not for fixing the Statistics link issue,
> you will need to apply
> > SAM-1620.
> >
> > Thanks,
> > Karen
> >
> >
> > On Mon, Mar 12, 2012 at 10:19 AM, David Wafula
> <davidwaf at gmail.com <mailto:davidwaf at gmail.com>> wrote:
> >>
> >> Hi Karen
> >> I realize i actually used
> >> https://jira.sakaiproject.org/browse/SAM-1552 to for
> the changes. And
> >> yes, it is Samigo 2.8.3, and it is not working.
> >>
> >> Thanks.
> >>
> >> On Mon, Mar 12, 2012 at 5:56 PM, Karen Tsao
> <ktsao at stanford.edu <mailto:ktsao at stanford.edu>> wrote:
> >> > Hi David,
> >> >
> >> > So you applied the all changes in SAM-1620
> successfully but still not
> >> > see
> >> > the Statistics link for assessments which contain
> random draw from pool?
> >> >
> >> > You have Samigo 2.8.3 but use the patch for trunk? I
> am not sure if this
> >> > is
> >> > reason. But I will work merging the changes to 2.8.x
> now. Maybe you can
> >> > try
> >> > to apply that?
> >> >
> >> > Thanks,
> >> > Karen
> >> >
> >> > On Mon, Mar 12, 2012 at 7:44 AM, David Wafula
> <davidwaf at gmail.com <mailto:davidwaf at gmail.com>>
> >> > wrote:
> >> >>
> >> >> Anyone out there? Thanks.
> >> >>
> >> >> On Mon, Mar 12, 2012 at 3:38 PM, David Wafula
> <davidwaf at gmail.com <mailto:davidwaf at gmail.com>>
> >> >> wrote:
> >> >> > Dear all,
> >> >> > I have tried over 3 days now and am out of options:
> >> >> > https://jira.sakaiproject.org/browse/SAM-1620
> >> >> >
> >> >> > This patch fails in my case. We are running Samigo
> 2.8.3 under Sakai
> >> >> > 2.8.0
> >> >> > I event went directly into the code and even
> modified the sql in
> >> >> > question, as suggested, but no luck. Statistics
> do not show when
> >> >> > random draw from pool is used.
> >> >> >
> >> >> > Anyone who has ever got this working, please help.
> >> >> >
> >> >> > --
> >> >> > David Wafula
> >> >> > University of Witwatersrand, Johannesburg.
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> David Wafula
> >> >> _______________________________________________
> >> >> sakai-dev mailing list
> >> >> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> >> >>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >> >>
> >> >> TO UNSUBSCRIBE: send email to
> >> >> sakai-dev-unsubscribe at collab.sakaiproject.org
> <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org>
> with a subject of
> >> >> "unsubscribe"
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> David Wafula
> >
> >
>
>
>
> --
> David Wafula
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org>
> with a subject of "unsubscribe"
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a
> subject of "unsubscribe"
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a
> subject of "unsubscribe"
>
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120314/18da37bf/attachment.html
More information about the sakai-dev
mailing list