[WG: Sakai QA] Release Managment Call, Thursday, 4 February 2010, 10 AM EST

[Berg, A.M.]

Hi all,

Each week QA and RM wants to talk Jira's at the Release management meeting. There is lots to talk about. Here are a few I see from scanning Jira, feel free to add more to the list. At least it is a start :)

SAK-17771   	 start-sakai missing a JAVA_OPTS and CATALINA_OPTS property for Java 1.6 compatability
KNL-101     Interpret content type if unknown
SAK-17457   	 Roster tool broken for site that migrated from 2.6
SAK-15874   	 Switch to Java 1.6 (Java 1.5 EOL 30-Oct-2009)
KNL-218          Synchronization blocks prevent > 1 request thread per user from executing
SAK-13386   	 High CPU from stuck threads
SAK-16982   	 transferCopyEntities does not create missing collection properly, leaves resource locking issues
SAK-16568   	 Entity picker link points to original site when 'Import from Site' option is used
SAK-16371   	 Allow ability to configure "DefaultPlainText" pastes into FCKEditor for particular tools
SAK-16214   	 Accessibility: FCK Editor inaccessible on Polls Add a Poll page
SAK-16212   	 Accessibility: FCK Editor inaccessible on Blogger create a post page
     ECT.
SAK-15914   	 Bizzare exception logic in BaseMessageService
SAK-15690   	 osp.matrix.evaluate is listed twice in the !user.template.maintain realm
SAK-14360   	 Announcements has dependency on assignements - DH 
SAK-14266   	 Fix JSR-168 support in the flat portal
SAK-13999   	 'You do not have permission' results showing up inappropriately'
SAK-8535   	 Include Confluence style WYSIWYG editor in RWiki 
SAK-14120   	 cacheMinutes settings no longer work
SAK-13978   	 Can't navigate back up folder hierarchy
SAK-13240   	 c3p0 : MySQL errors and warnings : java.sql.SQLException: Can't call commit when autocommit=true
SAK-12820   	 Accessibility: Dropdown list for Grading Table activates on down arrows (Gradebook)
SAK-11796   	 MOTD mucks up <a href> tags in non-FCKeditor
 

SAK-17879   	 saving of Name or description in Portfolio details does not work for free form Presentations
SAK-17875   	 Share with others also lists the same user as a choice to share a portfolio
SAK-17860
Deleting folder whose name is <script>alert('xss');</script> leaves an empty folder with no apparent name and a strange location
SAK-17696   	 If file size of attachment is greater than limit then no error message for end user, just in catalina.out
SAK-17640   	 Improve Webdav protocol consistency between Sakai versions
SAK-17515   	 Static code review: Logging using system out




> From: Anthony Whyte <arwhyte at umich.edu>
> Date: February 3, 2010 6:10:43 PM GMT-05:00
> To: announcements at collab.sakaiproject.org
> Cc: Sakai QA <sakai-qa at collab.sakaiproject.org>, Sakai Developers <sakai-dev at collab.sakaiproject.org 
> >
> Subject: [Building Sakai] Release Managment Call, Thursday, 4  
> February 2010, 10 AM EST
>
> I recommend we talk issues tomorrow, particularly the large backlog of
> resolved issues (n=296 as I write) that per Jira have yet to be
> tested, verified, closed and merged to 2.7.x.
>
> We may want to consider holding a special RM meeting to review these
> issues (issue by issue).  The large number could prove a challenge for
> QA, both community and local.  Perhaps this group of issues should be
> triaged for fixes that can be bumped to a 2.7.1 release.
>
> Cheers,
>
> Anth
>
> Connection Info
> 	. Telephone (Sakai001): +1 812 856 7060
> 	. Internet: 156.56.240.9
> 	. Conference Code: 348#
> 	. PIN: 72524#
> AgendaI. Outstanding action items:
> Release 2.5.6/2.6.2 (DONE)
>
> RM space pages:
>
> Versioning document (TODO)
>
> Generic doc re: prepping projects to use the Maven release plugin  
> (TODO)
>
> We need a 2.7.0 description/highlights doc/email to community. (TODO)
>
>
> II. Release scheduling and Issues review
> Discuss holding a special RM meeting to review 2.7.0 issues.  There
> are currently 296 resolved issues that need testing and verification
> before merging.  This could prove a challenge for QA, both community
> and local.  Perhaps this group of issues should be triaged for fixes
> that can be bumped to a 2.7.1 release.
>
> Sakai 2.7.0-b02
> Closed issues (merged): http://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12251
>
> Closed issues (to merge): http://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12212
>
> Resolved issues (to merge): http://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12213
>
> Resolved issues review|http://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12081
>
>
> QA update (Berg)
>
> III. Jira
> Maintenance team update
> Draft revised workflow
> _______________________________________________
> 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-qa/attachments/20100204/f11104b6/attachment.html