[WG: Sakai QA] [Management] QA 2.7.0 Compatability list.

Berg, A.M. A.M.Berg at uva.nl
Fri Nov 20 12:39:23 PST 2009


Hi Charles,

Good points, I agree with you. We need a stable QA environment for systematic testing. The logistic limitations of trying to clean up at this phase in the QA cycle would risk delays.

+1 for Tomcat 5.5.28 with this compatibility option during QA season 2.7.0 and then afterwards a recommended clean up.

Alan

Alan Berg
Interim QA Director - The Sakai Foundation

Senior Developer / Quality Assurance
Group Education and Research Services
Central Computer Services
University of Amsterdam

http://home.uva.nl/a.m.berg




-----Original Message-----
From: Charles Hedrick [mailto:hedrick at rutgers.edu]
Sent: Fri 11/20/2009 18:52
To: Berg, A.M.
Cc: Sakai QA; sakai-dev at collab.sakaiproject.org; management at collab.sakaiproject.org
Subject: Re: [Management] QA 2.7.0 Compatability list.
 
Let me express here the same concern I did at the meeting. Once we  
start QA of 2.7, we need to freeze switches like this. Since this  
option affects multiple applications, if we change it we have to go  
through another cycle of QA. That means that if we intend to deploy  
without the STRICT_QUOTE_ESCAPING option, we need to QA without it.  
That's fine with me, as long as we can get problems fixed. The dangers  
are:

* some code can't be QA'ed because it hasn't been fixed yet
* we realize late in the cycle that key code can't be fixed, and have  
to change the setting. This will should trigger another cycle of QA,  
which we probably can't do.

Before we commit to Tomcat 5.5.28 without this compatibility option,  
I'd like to see one of:

* a signoff from groups that are likely to be affected that they'll  
fix the problem within a week or two.
* appointment of generalists to fix these problems in all applications  
where they appear.

I'm willing to help with the second role, but in the past it's proven  
very difficult for people like me to get changes installed in svn.  
This particular problem is pretty straightforward, and can be fixed  
without any likely sideeffects on the code. So having people who just  
fix it whereever it turns up seems practical.


On Nov 19, 2009, at 1:03 PM, Berg, A.M. wrote:

> Note: Tomcat 5.5.27+ enforces strict quote escaping which creates  
> issues for certain Sakai JSF-based tools (e.g. OSP).  We recommend  
> that these issues be addressed in 2.7.0 so that deployers will not  
> be required to modify their JVM settings with - 
> Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20091120/d06e1bad/attachment.html 


More information about the sakai-qa mailing list