[sakai-core-team] The weird behavior of Trunk (from last Sakai Core Team Call) - NOW SOLVED

[JOSE MARIANO LUJáN GONZáLEZ]

Hi everyone!

Since I won't be able to attend tomorrow's meeting, I wanted to let you 
know that now things work well with Samigo in Trunk. Last week, I 
mentioned that during Testing, we were seeing some weird behavior in 
Samigo (when navigating through the tool). We now believe that it was 
probably related to SAM-2466 
<https://jira.sakaiproject.org/browse/SAM-2466> which was merged to 
trunk last night.

Today trunk is behaving as expected :) and we were able to verify some 
jiras.

-----

Here is what might have happened:

We were trying to verify some issues in the nightly severs (PRs already 
merged). Since Samigo was behaving weird (in nightly), we went back to 
our S2U qa server and saw that Samigo was working fine in that one. Our 
S2U qa server was the same built as nightly but including some patches 
that were already issued for PR but not merged yet (one of them was 
SAM-2466).

     - https://sakai-trunk.atica.um.es (included SAM-2466 for testing 
and it was working as expected)
     - https://trunk-mysql.nightly.sakaiproject.org/portal/ (did not 
include SAM-2466 yet)

So, after SAM-2466 has been merged to master, Samigo is behaving well in 
both servers!

Thanks for you input in the call (Matt and Earl),
best regards,
Mariano
<https://jira.sakaiproject.org/browse/SAM-2466>

-- 
******************************************
José Mariano Luján González - Aula Virtual
Area de Tecnologías de la Información
y las Comunicaciones Aplicadas (ATICA)
UNIVERSIDAD DE MURCIA - http://www.um.es

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20150304/53080610/attachment.html