2.5 Release Planning-21 (20080221)
ACTION ITEMS!!!!
Attendees
If you know you will be attending, please list your name
Megan May (Meeting facilitator)
Peter Knoop (Sakai project coordinator & regular attendee)
James Logan (regular attendee)
Renu (regular attendee)
David Haines (regular attendee)
David Horwitz_(regular attendee)_
Linda Place (regular attendee)
Anthony Whyte (Sakai community liason)
Jean-François Lévêque
John F. Hall
Charlie Shelton
Seth Theriault (semi-regular attendee)
Ian Boston
Jim Eng
Cheryl Johns (curious on-looker and hopeful 2.5 adopter for summer)
Beth Kirschner
Meeting Agenda
Update from Cape Town
Updates from testers/ developer
Release doc & artifact creation update
Review open critical/blockers: http://bugs.sakaiproject.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=11570
Release Date
Background on Discussion Points
Update From Cape Town
Content Conversion For Documentation
Moving from 2.4 to 2.5 requires adding several columns to the database tables used by the Content Hosting Service (the service used by the Resources tool, Dropbox, filepicker and webDav). The conversion scripts contain DDL statements to accomplish those changes. The new columns enable a switch from XML serialization to "binary-entity" serialization, which is faster and requires less memory. They also enable improved performance of quota calculations. A conversion utility is provided in 2.5.x to insert values in these new columns. You can get the benefits of binary-entity serialization without running the conversion utility, but you will never get the quota-calculation improvements without doing the full conversion. For clarify, this utility is separate from the conversion script.
Points
The conversion utility in 2.5.x was fully tested for MySQL. Cambridge migrated data using the conversion utility configured for MySQL. UCT has *not*
Oracle utility should be worked out by midmarch.
No testing of utility on QA servers?
If any Oracle users are interested moving to 2.5.0 before the changes are committed to 2.5.x, please contact Jim Eng for information about using the conversion utility that will be in post-2.4.
The Jiras related to this, such as
http://bugs.sakaiproject.org/jira/browse/SAK-12424 Adding resources does not use efficient query to check over-quota
http://bugs.sakaiproject.org/jira/browse/SAK-11395 Add database support for site-collection quota calculations
The conversion scripts for content provide SQL to add the new columns needed for binary-entity serialization and the new quota query.
Those are enough to get 2.5 running, but before getting full advantage of the quota query, the conversion utility must be run.
The order for doing this would be:
1) run the conversion script to add the new columns
2) start up sakai 2.5
3) run the conversion utility
When the conversion completes, sakai 2.5 will automatically start using the new code.
We have done a lot of tuning of the SQL in the oracle conversion. Ian said the Oracle conversion was tested on small sample data. We found severe performance issues when trying to run it against copies of our production database (~6 million records in the three tables). Our Oracle DBA suggested a number of improvements to the SQL used in the conversion. Those improvements are in a branch that has not been merged back to 2.5.x or trunk.
Review of Accessibility bugs.
Mike Elledge, the lead of the accessibility wg, was asked to rate the top 5 accessibility bugs so we can work to get these addressed in the 2.5.x branch (and hopefully a maintenance release). The top contenders are:
SAK-11679 Accessibility: Inaccessible dialogue box content (Wiki)
SAK-11665 Accessibility: "Add" and "Actions" rollovers not recognized as combo boxes (drop down lists) by screen reader (Resources)
SAK-11426 Accessibility: Tab Order and Functionality problems (Resources)
SAK-2773 Accessibility: Accesskey for worksites lands on "Logout" button (Global)
SAK-8233 Accessibility: Retain focus after changing tab location in Preferences > Customize Tabs
We also need to do something about the FCK Editor, either make it accessible or offer TinyMCE as an alternative (SAK-11783 Accessibility: Multiple accessibility problems with FCK editor). That's the biggest accessibility issue we face at present, but it seems like it is out of scope for this. Of course, I would be thrilled to find out that I'm wrong.
Release Status
Time line Review - Beta2 tag cut on 9th. RC1 should be cut and deployed by the time this meeting is held
Progress -
There are over 70 bug fixes going in from beta to beta2. We were down to 47 awaiting verification last week. This week there are 39 awaiting verification
We're seen a lot of progress in the list awaiting verification.
% Bugs Verified
Date
Awaiting Verification
# Verified
%
1/11/2008
453
720
~61%
1/30/2008
405
773
~66%
2/14/2008
431
799
~65%
2/20/2008
415
812
~66%
Areas to focus on - http://bugs.sakaiproject.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=11510