|
Noah, what' s the plan for testing this before it gets merged back to trunk and considered for 2.6.x? Do you feel you've done sufficient testing as part of this branch work?
Peter: I've made another pass to verify the changes in the branch. I believe it is ready to merge to trunk to do testing on nightly servers. Michigan will be doing broad testing against Sakai 2.5.x and 2.6.x as we plan to use the upgraded version locally. We are already running FCKeditor 2.6.2 in production (2.5.x) successfully. We would like to upgrade our local editor now and use the bundled version when we upgrade to 2.6.x.
We can commit to verifying the general integrity and function on a nightly/trunk server, as well as exercising the itemized enhancements that we feel are important for Sakai. If the upgrade is accepted for 2.6.x, we can commit to the same level of QA there to validate the merge. This branch has been running in production at Michigan for over a month with no problems reported.
Ready for QA, Noah Botimer requests that this be included in Sakai_ 2.6.1
QA OBSERVATIONS:
1) Listed (Update FCKeditor to 2.6.4) 2) Actual sakai/trunk on HSQLDB version: 2.6.2 sakai/trunk on HSQLDB - Built: 08/24/09 12:00 - Sakai Revision: 66004 - Server localhost 3) Latest version: 2.6.4.1 Fixed Bugs: * Security release, upgrade is highly recommended. For more details see CVE-2009-2265. http://www.fckeditor.net/whatsnew http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2265 4) Since version 2.6.4.1 of the FCKeditor is a highly recommended security upgrade, shouldn't it be included? Fixed in trunk and 2.6.x. Needs verification.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Task
Closed
Major
Update FCKeditor to 2.6.4.1
SAK-15993, which is a bug in FCKeditor 2.6, submitted for inclusion in their core release. This should be merged to trunk and 2.6.x.