[WG: Sakai QA] VOTE REQUEST - SAK-15027 - inclusion in Sakai 2.6.0-rc05? - VERIFIED
Pete Peterson
plpeterson at ucdavis.edu
Thu May 28 11:37:37 PDT 2009
SAK-15027 is now verified and closed, so ready for migration/merging into 2.6.x and rc05.
Thanks to everyone for all the help,
Pete
From: Pete Peterson
Sent: Thursday, May 28, 2009 11:04 AM
To: sakai-qa
Cc: Whyte, Anthony; Jones, Matthew; David Horwitz; 'Knoop, Peter'
Subject: RE: VOTE REQUEST - SAK-15027 - inclusion in Sakai 2.6.0-rc05? - RESULTS
Ok,
All agreed that this should be included, so I have added RC05 to the fix version and it is ready to merged as soon as it is verified in trunk.
Pete
From: Knoop, Peter [mailto:knoop at umich.edu]
Sent: Thursday, May 28, 2009 9:58 AM
To: Pete Peterson; sakai-qa
Cc: Whyte, Anthony; Jones, Matthew; David Horwitz
Subject: RE: VOTE REQUEST - SAK-15027 - inclusion in Sakai 2.6.0-rc05?
+1 to fix it for the release.
(I'm not sure what "criteria" keeps this one from being a Blocker? Much like the unwanted resource notifications and drop-box notifications did in the past, this would cause lots of support incidents, and be a general headache for any organization with even moderate wiki usage in their deployment.)
-peter
From: Pete Peterson [mailto:plpeterson at ucdavis.edu]
Sent: Thursday, May 28, 2009 12:38 PM
To: sakai-qa
Cc: Whyte, Anthony; Jones, Matthew; David Horwitz; Knoop, Peter
Subject: VOTE REQUEST - SAK-15027 - inclusion in Sakai 2.6.0-rc05?
Greetings,
Please chime in and vote on this issue SAK-15027<http://jira.sakaiproject.org/jira/browse/SAK-15027>. It does fall out of our Blocker criteria, but as Matt points out since it was functional in past versions and is now broken perhaps that criteria doesn't apply here.
Please vote or comment on inclusion in Sakai 2.6.0-RC05
Vote:
Comments:
========================================
Matt's comments pertaining to this issue:
SAK-15027<http://jira.sakaiproject.org/jira/browse/SAK-15027> (Wiki notifications are sent when they shouldn't be). Because of a security change that happened for 2.6, the preference check for rwiki notifications is ignored, so every page modification triggers a new notification to everyone in the site. This would be a major annoyance to any school that uses rwiki extensively (we do at Michigan).
It's a simple change which I've ran through all the notification tests for (as described in SAK-14298) and is something that worked correctly in all previous versions of 2.5.
=========================================
Thanks in advance,
Pete Peterson
QA Director, Sakai Foundation
plpeterson at ucdavis.edu<mailto:plpeterson at ucdavis.edu>
Phone: +1-530-754-7259
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20090528/07957198/attachment.html
More information about the sakai-qa
mailing list