On Thu, May 31, 2012 at 08:30:07AM -0700, Ray Davis wrote: > It's probably easiest if you just browse through the JIRA tickets: > > https://jira.sakaiproject.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SPARSE > > Because any storage solution must address both persistence and querying, > I would also include the Solr-integration bugs: > > https://jira.sakaiproject.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SOLR > > In both cases, many of the bugs have been fixed since this adventure > started in February 2011 while some still have not.
Would it be fair to say that of the handful of unresolved JIRAs in those two queues, none of them pertain to data integrity issues? > however, is that every time we try to add a feature (or just look more > closely at anomalies in our production environment), we've hit new bugs. Sounds like a functional QA process :) > Which shouldn't surprise anyone. No matter how skilled, a small > development team cannot simultaneously deliver new application > functionality on schedule and maintain an independently coded simulation > of Apache Jackrabbit. Shouldn't that cease to be a problem if the sparse map content code base is effectively frozen? Or does sparse map content need further extending to support new functionality? Best wishes, Daniel -- --| Daniel Parry: dan...@caret.cam.ac.uk. www.caret.cam.ac.uk/ |-- "Rare is the effective leader who didn't learn to become a good follower first." [John C. Maxwell] _______________________________________________ oae-dev mailing list oae-dev@collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/oae-dev
