[cle-release-team] New blockers/regressions since rc01 release 10/01/2012

[Matthew Jones]

This is just a reminder that any tickets which have been marked as
verified, merged and included in a  release should *not* be re-opened.
Verified tickets with all merges complete and in a release should really be
considered closed. Any new issues found (regressions) should be filed new
tickets and linked to the original. It makes it much more difficult to
follow progress on an old ticket for branch and release managers.

It's perfectly fine to re-open a ticket which is resolved before it is
verified and merged into a released version.

*Some outstanding possible regressions noted in mail and comments since
release rc01*

SAK-22674/KNL-600 - Possible regression on caching - New Blocker
Comment from Sam: "Okay, I bet join/unjoin is working for others because
KNL-965 and KNL-523 fire new events realm.join and realm.unjoin... we
probably need to listen for those new events for cache invalidation...."

KNL-817 - Copy Move (extensive) QA Needed
Long (16 part) test plan on ticket, back and forth from Earle and Aaron
over the weekend on KNL-955. This will take some time and someone that has
access to filesystem/database and server to test it (so not testable on a
regular QA server)

SAK-21739 - Email template some issues remain? -
Message from Chris last Friday - "I don’t think this is actually working
properly yet.  The db has a constraint, but all that really does is make my
startup fail because of a constraint violation.  Shouldn't it check to see
if the template exists before adding it?  That seems like the right way to
go.  Or, look for this exception and just skip over it as harmless."
Also Look at SAK-22679 to see if it was really incorporated/fixed by
SAK-22223.as it's still showing up on qa29 server
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20121001/f1c13f38/attachment-0006.html