I would prefer that we perform a maintenance release of the affected bundle (resource) as opposed to performing a full OAE 1.3.1 maintenance release. Are there any objections to this approach?
Cheers, Anthony On Jun 27, 2012, at 1:57 PM, Eli Cochran wrote: > In the process of integrating OAE 1.3 here at Berkeley, Yu-Hung discovered a > serious blocker bug in the 1.3 release. > > If sharing for a content item or document is set to private, you can't delete > it, even if you own it. > > Luckily we found that the issue had already been written up [1] and Zack had > already checked a fix in for 1.4 [2]. It was very easy to cherry-pick the fix > over. > > Any other institution running 1.3 should pick up this change. I would also > argue that this issue is serious enough that it might warrant a maintenance > release. > > [1] https://jira.sakaiproject.org/browse/KERN-2893 > [2] > https://github.com/sakaiproject/nakamura/commit/f8e2bb8b1de9345610bb58b8f9c7b26d83d877a3 > > . . . . . . . . . . . . . . . . . . > . > > Eli Cochran > project manager, CalCentral project > Educational Technology Services, UC Berkeley > > "Software is hard" - Donald Knuth >
_______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
